This commit is contained in:
@@ -0,0 +1,41 @@
|
||||
# octoturge-site
|
||||
|
||||
Landing page for octoturge.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 (manual, for now)
|
||||
|
||||
CI builds and uploads `dist/` as an artifact on every push to `main`, but
|
||||
does not yet sync it to the server automatically — the Gitea act runner
|
||||
uses ephemeral job containers with no host-visible workspace path, so an
|
||||
auto-deploy step needs an SSH deploy key added as a Gitea Actions secret
|
||||
first. Until that's set up, deploy manually:
|
||||
|
||||
```
|
||||
npm run build
|
||||
scp -r dist/* <host>:/mnt/e/sites/octoturge-com/
|
||||
```
|
||||
|
||||
Caddy serves `/mnt/e/sites/octoturge-com` as the document root for
|
||||
`octoturge.com`.
|
||||
Reference in New Issue
Block a user