There is still software powering your static site. That software has to live somewhere or on something. Maybe you upload it to GitLab Pages, then you're relying on the cloud to power your static site. Maybe you upload it to your local server where nginx is running. But something is still running it, and if you're doing it yourself - you can run it in a docker container.
I've taken both routes. I have a static site that uses Hugo to generate - just like you mention. It's distribution pipeline is a Docker container inside of GitLab CI/CD. So that it has all the tools needed to both run hugo and upload to AWS S3.
Other static sites I have are generated into HTML, dumped into a docker container with nginx. Then are pulled on relevant servers which run everything else in docker as well, along with the front end load balancer. It would actually be Significantly more work to NOT have the static site in Docker.
I kept infrastructure and data separate. Infrastructure I deploy on DO with ansible. nginx up front, letsencrypt auto renew TLS cert etc. Static content I deploy with rsync.
Takes ~3 seconds to deploy a content change by typing “make deploy”
No CI platform. No docker. Much simpler. Much faster. Much cheaper than AWS.
Comments
There is still software powering your static site. That software has to live somewhere or on something. Maybe you upload it to GitLab Pages, then you're relying on the cloud to power your static site. Maybe you upload it to your local server where nginx is running. But something is still running it, and if you're doing it yourself - you can run it in a docker container.
I've taken both routes. I have a static site that uses Hugo to generate - just like you mention. It's distribution pipeline is a Docker container inside of GitLab CI/CD. So that it has all the tools needed to both run hugo and upload to AWS S3.
Other static sites I have are generated into HTML, dumped into a docker container with nginx. Then are pulled on relevant servers which run everything else in docker as well, along with the front end load balancer. It would actually be Significantly more work to NOT have the static site in Docker.
I kept infrastructure and data separate. Infrastructure I deploy on DO with ansible. nginx up front, letsencrypt auto renew TLS cert etc. Static content I deploy with rsync.
Takes ~3 seconds to deploy a content change by typing “make deploy”
No CI platform. No docker. Much simpler. Much faster. Much cheaper than AWS.