Jayrude
/
jayrude-dot-dev
1
0
Fork 0
Code Pull Requests Actions Activity

Fix link

This commit is contained in:
Jarrod Doyle 2024-07-09 07:40:23 +01:00
parent 3a65fc9005
commit 9ce5a0e77c
Signed by: Jayrude
GPG Key ID: 38B57B16E7C0ADF7
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/blog/weeknotes/2024-11/index.md
View File

@ -23,7 +23,7 @@ After streaming (and lunch) I started looking into what tech I wanted to use for
- [SWAG](https://docs.linuxserver.io/general/swag/) for SSL certificates, reverse proxying, and authentication (with Fail2Ban), - [SWAG](https://docs.linuxserver.io/general/swag/) for SSL certificates, reverse proxying, and authentication (with Fail2Ban),
- and [Hugo](https://gohugo.io/) for the main site and blogging. - and [Hugo](https://gohugo.io/) for the main site and blogging.
With the exception of SWAG I've used all these technologies before so setting them up was fairly quick and painless. Previously I've done reverse proxying somewhat manually, but SWAG makes it incredibly easy. All of the services I'm using for now have existing proxy configs which I used, and adding an unsupported service is as simple as copying and modifying an existing template. With the basics set-up I posted my [first post]({{<ref "/hello-friends">}}) which felt good and cool. With the exception of SWAG I've used all these technologies before so setting them up was fairly quick and painless. Previously I've done reverse proxying somewhat manually, but SWAG makes it incredibly easy. All of the services I'm using for now have existing proxy configs which I used, and adding an unsupported service is as simple as copying and modifying an existing template. With the basics set-up I posted my [first post](/blog/hello-friends) which felt good and cool.
One thing I didn't get a chance to do at the time was automatic deployment of blog posts. The initial Hugo site and first blog post were manually uploaded to the server, which is not something I want to do each time I post. The less friction between writing and seeing a post the better. There's an existing GitHub Action for deploying a Hugo site to GitHub pages, which allows you to automatically build and deploy your site by making a commit to a repository. Gitea also has Actions, and you can even use most GitHub Actions with it which is super neat and cool. I had to setup an action runner (which just required adding another image to the stack in Portainer), but it wasn't very hard following the docs. What was a bit of a pain however was modifying the Hugo deployment action to work with my repository. For one thing, I wasn't using GitHub pages, so I needed to add a run action to copy the built website over to the appropriate place on my server using `rsync`. And for another, the repository checkout action wasn't working! My Gitea is hosted on a subfolder (`https://jayrude.dev/gitea`) rather than a sub-domain (`https://gitea.jayrude.dev`) and the subfolder was getting dropped. I found [this issue](https://github.com/actions/checkout/issues/1370) which says that it won't be fixed because they don't officially support non-GitHub servers. Luckily someone there linked a fork of the action which fixes it, so I just moved over to that instead and everything worked. One thing I didn't get a chance to do at the time was automatic deployment of blog posts. The initial Hugo site and first blog post were manually uploaded to the server, which is not something I want to do each time I post. The less friction between writing and seeing a post the better. There's an existing GitHub Action for deploying a Hugo site to GitHub pages, which allows you to automatically build and deploy your site by making a commit to a repository. Gitea also has Actions, and you can even use most GitHub Actions with it which is super neat and cool. I had to setup an action runner (which just required adding another image to the stack in Portainer), but it wasn't very hard following the docs. What was a bit of a pain however was modifying the Hugo deployment action to work with my repository. For one thing, I wasn't using GitHub pages, so I needed to add a run action to copy the built website over to the appropriate place on my server using `rsync`. And for another, the repository checkout action wasn't working! My Gitea is hosted on a subfolder (`https://jayrude.dev/gitea`) rather than a sub-domain (`https://gitea.jayrude.dev`) and the subfolder was getting dropped. I found [this issue](https://github.com/actions/checkout/issues/1370) which says that it won't be fixed because they don't officially support non-GitHub servers. Luckily someone there linked a fork of the action which fixes it, so I just moved over to that instead and everything worked.