Octoturge
44 lines
1.2 KiB
Markdown
44 lines
1.2 KiB
Markdown
# continuum-3d-site
|
|
|
|
Landing page for continuum-3d.com. Eleventy + Pug + Tailwind CSS, with a
|
|
small JSON-based i18n setup (`src/locales/en.json`, `src/locales/pl.json`).
|
|
|
|
- English lives at `src/en/index.pug` and builds to `/`.
|
|
- Polish lives at `src/pl/index.pug` and builds to `/pl/`.
|
|
- Add more languages by adding `src/locales/<lang>.json` and a
|
|
`src/<lang>/index.pug` with `lang: <lang>` in its front matter.
|
|
|
|
## Develop
|
|
|
|
```
|
|
npm install
|
|
npm run dev
|
|
```
|
|
|
|
## Build
|
|
|
|
```
|
|
npm install
|
|
npm run build
|
|
```
|
|
|
|
Output goes to `dist/`.
|
|
|
|
## Deploy
|
|
|
|
Every push to `main` builds the site and publishes `dist/` (zipped) as the
|
|
asset on a Gitea Release tagged `deploy`, using the automatic per-job
|
|
`GITEA_TOKEN` — no secrets to configure. A separate `site-deployer` watcher
|
|
container on octo-winsrv polls that release (`releases/tags/deploy`) every
|
|
~45s and, when it changes, extracts it into `/mnt/e/sites/continuum-3d-com/`,
|
|
which Caddy serves as the document root for `continuum-3d.com`. No SSH keys
|
|
or admin credentials are involved — the watcher only has filesystem access
|
|
to `/mnt/e/sites`, nothing else on the host.
|
|
|
|
Manual deploy still works if you need it immediately (bypasses the watcher):
|
|
|
|
```
|
|
npm run build
|
|
scp -r dist/* <host>:/mnt/e/sites/continuum-3d-com/
|
|
```
|