fix(post): fix typos and line breaks in 0001
This commit is contained in:
parent
f3d07d0594
commit
3a8a5ad8d6
1 changed files with 10 additions and 9 deletions
|
@ -131,17 +131,18 @@ self-contained—easier to install and maintain, which is great for CI.
|
|||
Long story short: I found a Hugo theme similar to Chirpy and migrated
|
||||
everything over even before the blog technically went live. Win-win?
|
||||
|
||||
### Infrastructure Both of the themes I looked at are designed for easy GitHub
|
||||
Pages deployment. Fork the theme, add your content, push—CI/CD handles the
|
||||
rest.
|
||||
### Infrastructure
|
||||
Both of the themes I looked at are designed for easy GitHub Pages deployment.
|
||||
Fork the theme, add your content, push—CI/CD handles the rest.
|
||||
|
||||
But where’s the fun in that? Hosting it on GitHub isn't very “old internet”,
|
||||
and I’m already self-hosting my own git forge, so everything’s ready to go.
|
||||
|
||||
#### Self-Hosting I had a few options for deployment. My first idea was to go
|
||||
self-contained: after the site is built, the files get copied into an nginx
|
||||
container and pushed to my forgejo container registry. Then it’s deployed via
|
||||
Docker Compose and updated by Renovate.
|
||||
#### Self-Hosting
|
||||
I had a few options for deployment. My first idea was to go self-contained:
|
||||
after the site is built, the files get copied into an nginx container and
|
||||
pushed to my forgejo container registry. Then it’s deployed via Docker Compose
|
||||
and updated by Renovate.
|
||||
|
||||
I tried this—and while it’s straightforward to implement—it didn’t sit well
|
||||
with me. Renovate only updates the digest after a new image is published, so
|
||||
|
@ -227,8 +228,8 @@ projects.
|
|||
- No promises about future posts. That **never** works out (I’ll explain why
|
||||
that is… in a future post).
|
||||
|
||||
## What to expect, and how often can be expected No expectations. No schedule.
|
||||
No guarantees of quality or consistency. You’ve been warned.
|
||||
## What to expect, and how often can be expected
|
||||
No expectations. No schedule. No guarantees of quality or consistency.
|
||||
|
||||
**Postscriptum**: I started writing this post on April 7th, but only managed to
|
||||
publish it now. Is that an indicator of how often I'm going to actually publish
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue