forked from coop-cloud/headscale
Compare commits
13 Commits
| Author | SHA1 | Date | |
|---|---|---|---|
| c80a135a99 | |||
| beb68cb6c4 | |||
| 53e74e9228 | |||
| b9118894ea | |||
| 0c7c64cd7e | |||
| 3897d3d6a9 | |||
| 4f48752ff8 | |||
| 311d08d461 | |||
| 899e0746cc | |||
| 0ef57f229f | |||
| d6092108f3 | |||
| 1fcc21e48f | |||
| b72fd39e38 |
@@ -25,3 +25,5 @@ ENABLE_DERP=false
|
||||
# See https://git.coopcloud.tech/coop-cloud/backup-bot-two
|
||||
ENABLE_BACKUPS=true
|
||||
|
||||
# The amount of time a node is authenticated, default is set to 7d
|
||||
#EXPIRY=0
|
||||
@@ -0,0 +1,35 @@
|
||||
# Headscale Recipe Maintenance
|
||||
|
||||
All contributions should be made via a pull request. This is to ensure a
|
||||
certain quality and consistency, that others can rely on.
|
||||
|
||||
## Maintainer Responsibilities
|
||||
|
||||
`3wc` is responsible for installing regular updates:
|
||||
|
||||
- Patch and minor updates within a week of them being released upstream
|
||||
- Major updates within a month of them being released upstream
|
||||
|
||||
`ammaratef45` is responsible for responding to pull requests and issues, within a week of them being filed.
|
||||
|
||||
`val` is available as backup for both of these tasks.
|
||||
|
||||
In order to fulfill these responsibilities a recipe maintainer:
|
||||
|
||||
- Has to watch the repository (to get notifications)
|
||||
- Needs to make sure Renovate is configured properly
|
||||
|
||||
## Pull Requests
|
||||
|
||||
A pull request can be merged if it is approved by at least one maintainer. For
|
||||
pull requests opened by a maintainer they need to be approved by another
|
||||
maintainer. Even though it is okay to merge a pull request with one approval, it
|
||||
is always better if all maintainers looked at the pull request and approved it.
|
||||
|
||||
## Become a maintainer
|
||||
|
||||
Everyone can apply to be a recipe maintainer:
|
||||
|
||||
1. Watch the repository to always get updates
|
||||
2. Simply add yourself to the list in the [README.md](./README.md), add yourself to whichever things you would like to be (co) responsible for in this document, then open a new pull request with the change.
|
||||
3. Once the pull request gets merged you will be added to the [headscale maintainers team](https://git.coopcloud.tech/org/coop-cloud/teams/headscale-maintainers).
|
||||
@@ -4,8 +4,10 @@
|
||||
|
||||
<!-- metadata -->
|
||||
|
||||
* **Maintainer**: [@3wc](https://git.coopcloud.tech/3wordchant), [@ammaratef45](https://git.coopcloud.tech/ammaratef45), [@val](https://git.coopcloud.tech/val)
|
||||
* **Status**: `stable`
|
||||
* **Category**: Apps
|
||||
* **Status**: 3
|
||||
* **Features**: 3
|
||||
* **Image**: [`headscale/headscale`](https://hub.docker.com/r/headscale/headscale), 4, upstream
|
||||
* **Healthcheck**: Yes
|
||||
* **Backups**: Yes
|
||||
@@ -41,4 +43,4 @@ abra app run yourapp.xyz app -- headscale help
|
||||
|
||||
2. The UI runs on `https://yourapp.xyz/web`, the UI is a mere frontend (a static site), so no data is saved on a server, so you will need to set URL and API-Key yourself on every client. Find more about the UI [here](https://github.com/gurucomputing/headscale-ui).
|
||||
|
||||
For the usage of headscale itself, check the [offical docs](https://headscale.net/stable/usage/getting-started/).
|
||||
For the usage of headscale itself, check the [offical docs](https://headscale.net/stable/usage/getting-started/).
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
# Set any config versions here
|
||||
# Docs: https://docs.coopcloud.tech/maintainers/handbook/#manage-configs
|
||||
export CONFIG_YAML_VERSION=v4
|
||||
export CONFIG_YAML_VERSION=v6
|
||||
|
||||
+5
-3
@@ -1,13 +1,15 @@
|
||||
---
|
||||
services:
|
||||
app:
|
||||
image: headscale/headscale:v0.28
|
||||
image: headscale/headscale:v0.29
|
||||
networks:
|
||||
- proxy
|
||||
command: serve
|
||||
volumes:
|
||||
# - config:/etc/headscale
|
||||
- data:/var/lib/headscale
|
||||
environment:
|
||||
EXPIRY: ${EXPIRY:-7d}
|
||||
configs:
|
||||
- source: config_yaml
|
||||
target: /etc/headscale/config.yaml
|
||||
@@ -20,7 +22,7 @@ services:
|
||||
- "traefik.http.routers.${STACK_NAME}.rule=Host(`${DOMAIN}`${EXTRA_DOMAINS})"
|
||||
- "traefik.http.routers.${STACK_NAME}.entrypoints=web-secure"
|
||||
- "traefik.http.routers.${STACK_NAME}.tls.certresolver=${LETS_ENCRYPT_ENV}"
|
||||
- "coop-cloud.${STACK_NAME}.version=0.1.0+v0.28"
|
||||
- "coop-cloud.${STACK_NAME}.version=0.4.1+v0.29"
|
||||
# Enable backups: https://docs.coopcloud.tech/maintainers/handbook/#how-do-i-configure-backuprestore
|
||||
- "backupbot.backup=${ENABLE_BACKUPS:-true}"
|
||||
- "backupbot.backup.path=/var/lib/headscale"
|
||||
@@ -32,7 +34,7 @@ services:
|
||||
start_period: 1m
|
||||
|
||||
ui:
|
||||
image: ghcr.io/gurucomputing/headscale-ui:2025.08.23
|
||||
image: ghcr.io/gurucomputing/headscale-ui:2026.03.17
|
||||
deploy:
|
||||
labels:
|
||||
- traefik.enable=true
|
||||
|
||||
+1
-6
@@ -348,7 +348,7 @@ oidc:
|
||||
# The amount of time a node is authenticated with OpenID until it expires
|
||||
# and needs to reauthenticate.
|
||||
# Setting the value to "0" will mean no expiry.
|
||||
expiry: 7d
|
||||
expiry: {{ env "EXPIRY" }}
|
||||
|
||||
# Use the expiry from the token received from OpenID when the user logged
|
||||
# in. This will typically lead to frequent need to reauthenticate and should
|
||||
@@ -410,11 +410,6 @@ logtail:
|
||||
# disabled by default. Enabling this will make your clients send logs to Tailscale Inc.
|
||||
enabled: false
|
||||
|
||||
# Enabling this option makes devices prefer a random port for WireGuard traffic over the
|
||||
# default static port 41641. This option is intended as a workaround for some buggy
|
||||
# firewall devices. See https://tailscale.com/kb/1181/firewalls/ for more information.
|
||||
randomize_client_port: false
|
||||
|
||||
# Taildrop configuration
|
||||
# Taildrop is the file sharing feature of Tailscale, allowing nodes to send files to each other.
|
||||
# https://tailscale.com/kb/1106/taildrop/
|
||||
|
||||
@@ -0,0 +1 @@
|
||||
added EXPIRY env (non-breaking)
|
||||
Reference in New Issue
Block a user