Skip to content

Readme #19

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
UltiPro merged 1 commit into from
Oct 24, 2026
Merged

Readme #19

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -253,7 +253,8 @@ A push to `main` runs three gates in parallel - ruff and pytest, the frontend's
tests and linters, and a smoke test over HTTP against the freshly built image - and only then builds
for real: two images, `folderly-backend` and `folderly-web` (Caddy with the built SPA inside), each
on native `amd64` and `arm64` runners, published to GHCR as one manifest per image under `latest`
and `sha-<commit>`. Hosts follow `latest`, pinning a `sha-` tag is the rollback.
and `sha-<commit>`, the full forty characters. Hosts follow `latest`, pinning a `sha-` tag is
the rollback.

**Nothing in the workflow names this account.** It publishes to
`ghcr.io/<repository owner>/folderly-backend` and `-web`, so a fork builds its own pair under its
Expand Down
2 changes: 1 addition & 1 deletion deploy/.env.example
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@
FOLDERLY_IMAGE=ghcr.io/OWNER/folderly-backend
FOLDERLY_WEB_IMAGE=ghcr.io/OWNER/folderly-web

# `latest` follows every green build; sha-abc1234 pins one commit, both images.
# `latest` follows every green build, sha-<40-char commit> pins both images.
IMAGE_TAG=latest

# The domain Caddy certifies. Empty = plain HTTP on :80, for trying it locally.
Expand Down
7 changes: 4 additions & 3 deletions docs/deployment.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -172,9 +172,10 @@ journalctl -u folderly-update.service -f # what the timer did
sudo systemctl start folderly-update.service # update now, without waiting
```

**Rolling back** is one line in `.env`: `IMAGE_TAG=sha-<commit>` from a build that worked, then
`up -d` again. One tag covers both images, so a tested pair stays together. Go back to `latest`
afterwards, or the timer holds the old version forever.
**Rolling back** is one line in `.env`: `IMAGE_TAG=sha-<commit>` from a build that worked - the
full forty characters, not the short form - then `up -d` again. One tag covers both images, so a
tested pair stays together. Go back to `latest` afterwards, or the timer holds the old version
forever.

**When it does not come up**, in order of likelihood: the `chown` in step 2 was skipped (the
container restart-loops on "unable to open database file"), port 80 does not reach the host from
Expand Down