Deploy StarPunk from its CI-built image
StarPunk's Gitea Actions workflow now builds and pushes the image on vX.Y.Z tags. Pin the tag in starpunk_version (v2.0.2, the first CI build) and always pull it, so an image built by hand on the server with the same name can't be deployed instead. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -58,7 +58,7 @@ Tags: each category file has a category tag, each service its own tag.
|
||||
|---|---|---|
|
||||
| `gotosocial` | GoToSocial | Pocket ID through env vars. Account domain is the apex; Caddy serves WebFinger there. Daily S3 backup of its volume. |
|
||||
| `listmonk` | Listmonk | Postgres 17. On `listmonk.nerder.land`. |
|
||||
| `starpunk` | StarPunk | Micropub server for the main site (own image from Gitea). Admin login via Pocket ID; issues its own Micropub tokens. |
|
||||
| `starpunk` | StarPunk | Micropub server for the main site. Image built by the StarPunk repo's Gitea Actions on `vX.Y.Z` tags; deploy a release by bumping `starpunk_version`. Admin login via Pocket ID; issues its own Micropub tokens. |
|
||||
|
||||
### Monitoring (`monitoring`)
|
||||
| Tag | Service | Notes |
|
||||
|
||||
Reference in New Issue
Block a user