No description
- HTML 53.1%
- Sass 30.6%
- Python 11.5%
- CSS 2.3%
- Makefile 2.3%
- Other 0.2%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
|
All checks were successful
Build and deploy / build-and-deploy (push) Successful in 2m21s
A reader emailed after getting stuck at step 3 of "Adding STL 3D Previews to Forgejo": the only link to the full `stlview.js` was in the intro paragraph, and the code block in that step is an explanatory excerpt rather than the whole file, so it was unclear what the file should contain. - Step 2 (footer template): the `stlview.js` mention now links to the Codeberg source. - Step 3: links the Codeberg source, tells the reader to copy that file into `custom/public/assets/stlview.js`, and says the snippets below are partial. - After the asset file tree: a short note on where each file comes from (Codeberg for `stlview.js`, the three.js r160 release for the bundled modules). Content-only change; no template or config changes. Both external links verified to return 200. Hugo is not installed in this environment, so the site build was not run locally — the PR build covers it. Closes FMG-8 Reviewed-on: #4 Reviewed-by: Felipe M <me@fmartingr.com> |
||
| .github/workflows | ||
| archetypes | ||
| assets | ||
| content | ||
| layouts/partials | ||
| resources/_gen/assets/sass | ||
| themes/fmartingr | ||
| .gitignore | ||
| .hugo_build.lock | ||
| go.mod | ||
| go.sum | ||
| hugo.toml | ||
| lektor2hugo.py | ||
| Makefile | ||
| README.md | ||
fmartingr.com
Source code for my personal site hosted at fmartingr.com
Development
make server # local preview, including drafts and future-dated posts
make new-post # scaffold a post under content/blog/YYYY/MM/DD/
The theme transpiles Sass, so a Hugo extended build is required.
Deployment
.github/workflows/deploy.yml builds the site and rsyncs public/ to the web
host over SSH.
The build runs on every pull request against master, so a broken site is
caught before merge. The deploy step is skipped there and only runs for pushes
to master, the daily schedule (so posts dated in the future get published once
their date arrives), and manual dispatches.
The deploy rsyncs with --delete, so anything under SSH_PATH that the build
does not produce is removed from the server.
It needs the following Actions secrets:
| Secret | Description |
|---|---|
SSH_HOST |
Hostname of the web server |
SSH_USER |
SSH login user |
SSH_PATH |
Remote directory the site is copied into |
SSH_PRIVATE_KEY |
Private key contents for SSH_USER |