For some time I’ve been wanting to explore kickstart files for automated server installations. I finally got around to trying it out.
The simplest way to make kickstart files accessible during installation is to serve them over HTTP from a web server.
In the previous post we looked at running ansible from our PC to perform system tasks on a remote system.
To avoid having to install ansible on the host system it makes more sense to use a container for it though.
A lot of system administration can be automated using Ansible. Of course it’s also possible to just use shell scripts to do the same.
The difference is not that big and depends a lot on how you want to work.
Now that I have my container images ready, I can build my site and deploy it.
Let’s make a Jenkins pipeline to handle the deployment.
To host my Hugo generated static site I’ll need a web server.
For this task I have chosen to use nginx.
I am using Hugo to build this website and it made sense for me to automate it.
The first step on that journey is to create a container to use for the static site files generation.
