<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Hugo - Category - JMS Blog</title><link>/categories/hugo/</link><description>Hugo - Category - JMS Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Sat, 10 Oct 2026 12:16:05 -0600</lastBuildDate><atom:link href="/categories/hugo/" rel="self" type="application/rss+xml"/><item><title>Blog migration: From VPS to Cloudflare pages</title><link>/posts/about-blog/</link><pubDate>Sat, 10 Oct 2026 12:16:05 -0600</pubDate><author>jms</author><guid>/posts/about-blog/</guid><description><![CDATA[<p>The current setup for my blog offers great flexibility and control, source and CI/CD is on <a href="https://gitlab.com/" target="_blank" rel="noopener noreffer ">GitLab</a>, DNS is handled by <a href="https://www.cloudflare.com/" target="_blank" rel="noopener noreffer ">Cloudflare</a> and server is VPS in <a href="https://www.hetzner.com/" target="_blank" rel="noopener noreffer ">Hetzner Cloud</a> (2 vcpu/4 GB ram/40 GB disk) using <a href="https://fedoraproject.org/" target="_blank" rel="noopener noreffer ">Linux Fedora</a> 44 on aarch64, but probably is overkill just to run Nginx and serve static content.</p>
<h2 id="migration">Migration</h2>
<p>I&rsquo;m migrating my blog to another platform with 2 main goals and one constraint, first goal is to reduce mantainance operations like apply OS updates, security patches, check logs, configurations updates, remove old logs, second goald is reduce costs to minimum, the constraint avoid any vendor lock-in or any major change on the blog tooling, currently using <a href="https://gohugo.io/" target="_blank" rel="noopener noreffer ">Hugo site generator</a>.</p>]]></description></item><item><title>Markdown Blog</title><link>/posts/2018-02-25-blog-setup/</link><pubDate>Sun, 25 Feb 2018 00:00:00 +0000</pubDate><author>jms</author><guid>/posts/2018-02-25-blog-setup/</guid><description><![CDATA[<p>For this blog, i&rsquo;ve setup a linux KVM vps, using as distro Fedora 27.
Fedora 27 comes with Selinux enforced security policy by default this is OK for
system or apps where you required a high security level, but for my case to serve a
static blog and run a couple of services like OpenSSH and Nginx is ok to set the security
policy on permissive mode.</p>
<p>changing the policy can be done via command or setup in permanent way on the selinux config
in <code>/etc/selinux/config</code></p>]]></description></item><item><title>Markdown Blog</title><link>/posts/2018-02-18-markdown-blog/</link><pubDate>Sun, 18 Feb 2018 00:00:00 +0000</pubDate><author>jms</author><guid>/posts/2018-02-18-markdown-blog/</guid><description>&lt;p>There are many reasons and options to choose a static site generator,
but the main reasons are speed and security. Speed because it can allow more control
over the content you only load what is really required without additional
server side content, for security not having a database that can be compromised and
security updates to apply, reduce the attack vectors and the administration work.&lt;/p>
&lt;p>There are many options for static site generators created on diferent languages like:&lt;/p></description></item></channel></rss>