templates/frontend-svelte
2
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(frontend): .env reaches the build, runtime image without it; eslint + prettier as an option #1

Merged
hh merged 3 commits from deploy-scheme into main 2026-10-08 18:46:04 +00:00
Conversation 0 Commits 3 Files Changed 17
+2
1 changed files with 2 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Showing only changes of commit ab67b5a5da - Show all commits
template/{{ part_dir }}/{% if layout == 'root' %}README.md{% endif %}.jinja
+2
View File
@@ -11,4 +11,6 @@ make recreate
To deploy, `git pull && make deploy`. It runs `make pre-deploy`, which rebuilds the image only when something in the repository changed, then `docker compose up -d`. A deploy system with its own `up` step calls `make pre-deploy` before it and `make post-deploy` after. What was built is remembered as `refs/deploy/*` in the clone. To deploy, `git pull && make deploy`. It runs `make pre-deploy`, which rebuilds the image only when something in the repository changed, then `docker compose up -d`. A deploy system with its own `up` step calls `make pre-deploy` before it and `make post-deploy` after. What was built is remembered as `refs/deploy/*` in the clone.
In the fleet, production is deployed from `infra/komodo` instead (git mode of Komodo, see `docs/architecture.md` there): Komodo clones this repo, and a layer plus `deploy.sh` in the stack's directory tag images by the hash of what they bake in and write `.env` from sops. The repo only has to stay a plain recipe: images built from `build:` in compose, `caddy/site.caddy`. `make deploy` and `refs/deploy/*` are for a checkout deployed by hand.
`make dev` runs the Vite dev server on the host, `make fmt` formats, `make check` runs svelte-check and the linter. `make dev` runs the Vite dev server on the host, `make fmt` formats, `make check` runs svelte-check and the linter.