Source for https://manuelgomes.eu (Bridgetown)
- JavaScript 59%
- Ruby 34.4%
- Shell 3.1%
- HTML 3%
- CSS 0.5%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
|
|
||
| bin | ||
| config | ||
| frontend | ||
| plugins | ||
| server | ||
| src | ||
| tmp/pids | ||
| .gitignore | ||
| .ruby-version | ||
| config.ru | ||
| esbuild.config.js | ||
| Gemfile | ||
| Gemfile.lock | ||
| jsconfig.json | ||
| package-lock.json | ||
| package.json | ||
| postcss.config.js | ||
| Rakefile | ||
| README.md | ||
manuelgomes.eu
Source for https://manuelgomes.eu, built with Bridgetown.
Development
bundle install && npm install
bin/bridgetown start # http://localhost:4000
Deployment
bin/deploy
This builds the site for production and force-pushes output/ to the
pages branch on origin (code.manuelgomes.eu/manuel/manuelgomes.eu).
A push webhook on the repo then tells git-pages on the server to fetch the
branch and serve it. The webhook fires on every push (Forgejo ignored the
branch filter), but git-pages only acts on refs/heads/pages.
How the apex gets mapped to this repo:
- DNS:
manuelgomes.euA/AAAA point at the server. - DNS: TXT
_git-pages-repository.manuelgomes.eu=https://code.manuelgomes.eu/manuel/manuelgomes.eu.gitauthorises this repo to publish to the apex. - Forgejo webhook: push events go to
https://manuelgomes.eu/(Forgejo type, JSON).
Server-side details live in the tiny project README.