Deploying a Static Blog with Continuous Integration
1–10 of 18 posts
Re: Deploying a Static Blog with Continuous Integration
#2I don't mean to be pedantic but I do get confused by people writing about tenants and building in one sentence, when they probably meant tenets?
"...we can leverage another one of it’s key tenants, which is that the building,..."
Re: Deploying a Static Blog with Continuous Integration
#3I don't mean to be pedantic but I do get confused by people writing about tenants and building in one sentence, when they probably meant tenets? "...we can leverage another one of it’s key tenants, which is that the building,..."
Oops, fixed :p
Re: Deploying a Static Blog with Continuous Integration
#4For a single provider solution GitLab pages has built-in CI and hosting.
They have gitlab-ci.yml files for most of the static page generators. Whether you use Hugo, Jeckyll, Pelican, etc there is a ci config to start with virtually no setup overhead for hosting or ci.
Re: Deploying a Static Blog with Continuous Integration
#5Netlify[0] is the best solution I've found so far for my personal site. It's specifically designed for this purpose. One of the nice features they have is the ability to set headers on different pages as well as proxy certain paths to external services via configuration files.
Re: Deploying a Static Blog with Continuous Integration
#6Netlify[0] is the best solution I've found so far for my personal site. It's specifically designed for this purpose. One of the nice features they have is the ability to set headers on different pages as well as proxy certain paths to external services via configuration files.
Re: Deploying a Static Blog with Continuous Integration
#7Netlify[0] is the best solution I've found so far for my personal site. It's specifically designed for this purpose. One of the nice features they have is the ability to set headers on different pages as well as proxy certain paths to external services via configuration files. [0] https://www.netlify.com/
+1 for Netlify. I've been using it for a few months for my personal site. It took me maybe 10 minutes from creating an account to going live with SSL from a GitHub repository. I brought it work with me, using it to host a React prototype (and hopefully, eventually, production).
Re: Deploying a Static Blog with Continuous Integration
#8For a single provider solution GitLab pages has built-in CI and hosting. https://gitlab.com/pages/hugo They have gitlab-ci.yml files for most of the static page generators. Whether you use Hugo, Jeckyll, Pelican, etc there is a ci config to start with virtually no setup overhead for hosting or ci.
Didn't know about this. Very cool, thanks.
Re: Deploying a Static Blog with Continuous Integration
#9Although the site generation software here is Hugo it could easily be another provider such as Jekyll. The web server will be hosted on a Digital Ocean droplet running Nginx, and CircleCI will be used for for the continuous integration (often abbreviated to simply “CI”)
It's just a blog. Why is this better than running Wordpress, perhaps with a caching server in front if the traffic is heavy enough?
Re: Deploying a Static Blog with Continuous Integration
#10Although the site generation software here is Hugo it could easily be another provider such as Jekyll. The web server will be hosted on a Digital Ocean droplet running Nginx, and CircleCI will be used for for the continuous integration (often abbreviated to simply “CI”) It's just a blog. Why is this better than running Wordpress, perhaps with a caching server in front if the traffic is heavy enough?
There's no CMS software exposed on the public-facing end, so no need to continually monitor and install security updates the way there is with WP and other CMS-driven systems. That's not a huge thing, especially these days when WP increasingly updates itself, but if you're looking to reduce your attack surface it can be helpful.