docs: note that the server's compose and env are copied by hand
The variable rename landed in the repository but not on the server, which keeps its own compose.yaml and .env. Neither is pulled from here, so the container came up against the old names. A release touching either now has to say so in its notes.
This commit is contained in:
@@ -75,6 +75,16 @@ title — the CalVer tag is not created until `make image` runs after the merge.
|
||||
|
||||
The types above are for `dev`, where a commit really does do one thing.
|
||||
|
||||
## Deploying
|
||||
|
||||
The server keeps its own `compose.yaml` and `.env`. Neither is pulled from
|
||||
here, so a release that renames a variable, adds one, or changes a mount
|
||||
needs both copied across **in the same deploy** — otherwise the container
|
||||
comes up against the old names and the app refuses to start.
|
||||
|
||||
Anything in this repository that reaches the server by hand belongs in the
|
||||
release notes, flagged as breaking.
|
||||
|
||||
## Things that are easy to get wrong
|
||||
|
||||
- **The interface is Finnish.** Code, comments, this file and the PRD are
|
||||
|
||||
Reference in New Issue
Block a user