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

[Feature] provide docker containers with two standard tags "latest" and "production" #728

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

Originally created by @noseshimself on GitHub (Jun 15, 2024).

Use case

I would like to integrate headscale docker images in my day-to-day operations.

Description

Even if there is no production-ready version yet, these two tags would make life much easier.

Contribution

  • I can write the design doc for this feature
  • I can contribute this feature

How can it be implemented?

When pushing out updates to Dockerhub just add a new "latest" and if you consider something sufficiently stable add the same image under the "production" tag. I don't think it will need contributions or an elaborate design specification.

Originally created by @noseshimself on GitHub (Jun 15, 2024). ### Use case I would like to integrate headscale docker images in my day-to-day operations. ### Description Even if there is no production-ready version yet, these two tags would make life much easier. ### Contribution - [X] I can write the design doc for this feature - [X] I can contribute this feature ### How can it be implemented? When pushing out updates to Dockerhub just add a new "latest" and if you consider something sufficiently stable add the same image under the "production" tag. I don't think it will need contributions or an elaborate design specification.
adam added the enhancement label 2025-12-29 02:23:00 +01:00
adam closed this issue 2025-12-29 02:23:00 +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 enhancement
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#728
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?