Give Hammerhead its own edge with a built-in dashboard route; setup.sh installs it with Blacktip instead of Caddy
HAMMERHEAD_SELF_DOMAIN creates an edge for this machine, writes its token to <data>/self-edge.env and adds an https route for the dashboard to that edge's config, so no reverse proxy is needed. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
9ad690def0
commit
536284ec75
8 files changed
+342
-74
No files matched your search
@@ -45,15 +45,15 @@ Releases are built by Gitea Actions. Pushing a tag such as `v0.2.0` runs `.gitea
|
||||
|
||||
**Fastest: one script on a fresh VPS**
|
||||
|
||||
`deploy/setup.sh` (also inside the Linux archives) installs everything for you on a systemd Linux: the service, a generated master key, the firewall rules, and optionally HTTPS.
|
||||
`deploy/setup.sh` (also inside the Linux archives) installs everything for you on a systemd Linux: the services, a generated master key, the firewall rules and HTTPS.
|
||||
|
||||
```
|
||||
sudo sh setup.sh --domain hammerhead.example.com # Hammerhead + Caddy for HTTPS
|
||||
sudo sh setup.sh edge --hammerhead https://hammerhead.example.com --token <edge token> --ports 25565,30000-30100
|
||||
sudo sh setup.sh agent --hammerhead https://hammerhead.example.com --token <site token>
|
||||
sudo sh setup.sh --domain hammerhead.example.com # Hammerhead and an edge on this machine
|
||||
sudo sh setup.sh agent --hammerhead https://hammerhead.example.com --token <site token> # on each site
|
||||
sudo sh setup.sh edge --hammerhead https://hammerhead.example.com --token <edge token> # more public servers
|
||||
```
|
||||
|
||||
`edge` installs Blacktip (with its bundled Traefik) and lists every IP address on the machine that ports can be opened on; `agent` installs Bamboo on the machine that hosts your services. All three can run on one machine or on three.
|
||||
With `--domain`, Hammerhead listens only on `127.0.0.1:8080` and gets an edge of its own (`HAMMERHEAD_SELF_DOMAIN`): the Blacktip on the same machine serves the dashboard at `https://<domain>` with an automatic certificate, so no Caddy or other web server is needed. The route is built in, not a mapping you can edit or delete by mistake. DNS for the name must point at the server and ports 80 and 443 must be free. `--caddy` keeps the old style: Hammerhead alone, with Caddy providing HTTPS. Add `--ports 25565,30000-30100` to open game or mail ports in the firewall, and `--no-auto-update` to leave updates to you.
|
||||
|
||||
**On a Linux server (systemd)**
|
||||
|
||||
|
||||
Reference in new issue
Block a user