@@ -41,7 +41,7 @@ Continue reading for an overview of the deployment and basic usage.
This is a Multi-tier deployment for after dark in order to run on k3s or other kubernetes cluster in a microservices way. Currently is meant to run on a single node cluster but you can still test a few things (see below) on a multinode cluster. Your site is being built by hugo and served by a separate nginx web server which is exposed as a service inside your cluster. Combined with a traefik ingress host rule it can be faced against the web abstracting its backend. The deployment is consisted of the following manifests:
* ``after-dark-k3s-hugo.yaml`` deploys a pod using two containers. First, an ephemeral initialization tasked with downloading After Dark from [source repo](https://git.habd.as/comfusion/after-dark) and, finally, the actual hugo container which kicks in and installs the site. When done it runs [`hugo server`](https://gohugo.io/commands/hugo_server/) in _watch mode_ so [Hugo](https://gohugo.io/) rebuilds After Dark site as files change.
* ``after-dark-k3s-hugo.yaml`` deploys a pod containing hugo that will first begin with downloading After Dark from [source repo](https://git.habd.as/comfusion/after-dark), install it and finally kick hugo in watch mode. This means that our pod will serve as our builder since [Hugo](https://gohugo.io/) rebuilds After Dark site as files change.
* ``after-dark-nginx.yaml`` deploys an [nginx](https://www.nginx.com/) web server that serves the content of the rendered site. As file changes occur Hugo will rebuild the After Dark site and nginx will pick up the changes.
* ``after-dark-service.yaml`` exposes nginx to a [NodePort](https://kubernetes.io/docs/concepts/services-networking/service/#nodeport) so we can actually reach the site from a browser.