starred/headscale
1
0
Fork 0
mirror of https://github.com/juanfont/headscale.git synced 2026-01-11 20:00:28 +01:00
Code Issues 98 Packages Projects Releases 10 Wiki Activity

[PR #57] [CLOSED] Added init subcommand to generate base config #1229

New Issue
Closed
opened 2025-12-29 02:29:17 +01:00 by adam · 0 comments
adam commented 2025-12-29 02:29:17 +01:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/juanfont/headscale/pull/57
Author: @juanfont
Created: 7/19/2021
Status: ❌ Closed

Base: main ← Head: init-subcommand

📝 Commits (2)

  • 52f372c Added init command to generate a working env
  • 09ec217 Fixing linting issue

📊 Changes

3 files changed (+86 additions, -1 deletions)

View changed files

📝 app.go (+5 -0)
➕ cmd/headscale/cli/init.go (+75 -0)
📝 cmd/headscale/headscale.go (+6 -1)

📄 Description

headscale init sqlite generates a working headscale environment (i.e., config.json, derp.yaml and wireguard private.key)

This helps my life a lot when developing in a reusable Vagrant environment.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/juanfont/headscale/pull/57 **Author:** [@juanfont](https://github.com/juanfont) **Created:** 7/19/2021 **Status:** ❌ Closed **Base:** `main` ← **Head:** `init-subcommand` --- ### 📝 Commits (2) - [`52f372c`](https://github.com/juanfont/headscale/commit/52f372cdbe1272b76661f399b9d1dca5d3913fb0) Added init command to generate a working env - [`09ec217`](https://github.com/juanfont/headscale/commit/09ec217bb1c5b28339acfce2038fe1fa462a6b0d) Fixing linting issue ### 📊 Changes **3 files changed** (+86 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `app.go` (+5 -0) ➕ `cmd/headscale/cli/init.go` (+75 -0) 📝 `cmd/headscale/headscale.go` (+6 -1) </details> ### 📄 Description `headscale init sqlite` generates a working headscale environment (i.e., config.json, derp.yaml and wireguard private.key) This helps my life a lot when developing in a reusable Vagrant environment. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
adam added the pull-request label 2025-12-29 02:29:17 +01:00
adam closed this issue 2025-12-29 02:29:17 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
CLI
DERP
DNS
Nix
OIDC
SSH
bug
database
documentation
duplicate
enhancement
faq
good first issue
grants
help wanted
might-come
needs design doc
needs investigation
no-stale-bot
out of scope
performance
policy 📝
pull-request
Mirrored from GitHub Pull Request
 question
regression
routes
stale
tags
tailscale-feature-gap
well described ❤️
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#1229
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?