Pipelines to deploy static website #83

New issue

Closed

opened 2024-04-18 21:40:51 +00:00 by pim · 1 comment

pim commented

2024-04-18 21:40:51 +00:00

Owner

We have a static website with Hugo, but by now it's unmaintained. Clean it up a bit and make a nix development environment for it. We then propose two pipelines:

On push, build a container image that serves the compiled static website using e.g. NGINX. This should be possible purely with Nix. Then publish this image to Forgejo's image registry for the repository.
When a new release is pushed, deploy it automatically to Kubernetes. This part might not actually be possible or easy. It seems you can't hook into a new image being pushed to Forgejo yet. You can however hook into a new release, which might be a workaround. Also not sure how we can tell Kubernetes to deploy the latest version. We could bump the version in the repository, but this seems hacky.

We have a static website with Hugo, but by now it's unmaintained. Clean it up a bit and make a nix development environment for it. We then propose two pipelines: - On push, build a container image that serves the compiled static website using e.g. NGINX. This should be possible purely with Nix. Then publish this image to Forgejo's image registry for the repository. - When a new release is pushed, deploy it automatically to Kubernetes. This part might not actually be possible or easy. It seems you can't hook into a new image being pushed to Forgejo yet. You can however hook into a new release, which might be a workaround. Also not sure how we can tell Kubernetes to deploy the latest version. We could bump the version in the repository, but this seems hacky.

pim commented

2024-04-18 21:48:25 +00:00

Author

Owner

Same idea: https://feval.ca/posts/k8s-static/