<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Git - Category - JMS Blog</title><link>/categories/git/</link><description>Git - 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/git/" 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>Git sync forked repo</title><link>/posts/2018-04-07-git-sync-fork/</link><pubDate>Sat, 07 Apr 2018 00:00:00 +0000</pubDate><author>jms</author><guid>/posts/2018-04-07-git-sync-fork/</guid><description>&lt;p>Some git notes&lt;/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><item><title>Some basics git commands</title><link>/posts/2014-09-29-git-my-cheatsheet/</link><pubDate>Mon, 29 Sep 2014 00:00:00 +0000</pubDate><author>jms</author><guid>/posts/2014-09-29-git-my-cheatsheet/</guid><description><![CDATA[<p>Basic workflow</p>
<div class="code-block code-line-numbers open" style="counter-reset: code-block 0">
    <div class="code-header language-bash">
        <span class="code-title"><i class="arrow fas fa-angle-right" aria-hidden="true"></i></span>
        <span class="ellipses"><i class="fas fa-ellipsis-h" aria-hidden="true"></i></span>
        <span class="copy" title="Copy to clipboard"><i class="far fa-copy" aria-hidden="true"></i></span>
    </div><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl"><span class="c1"># setup the project  </span>
</span></span><span class="line"><span class="cl">git clone github/project.git  
</span></span><span class="line"><span class="cl">git branch FeatureX  
</span></span><span class="line"><span class="cl">git co FeatureX
</span></span><span class="line"><span class="cl">
</span></span><span class="line"><span class="cl"><span class="c1"># make some changes  </span>
</span></span><span class="line"><span class="cl">git status  
</span></span><span class="line"><span class="cl">git add .
</span></span><span class="line"><span class="cl">
</span></span><span class="line"><span class="cl"><span class="c1"># commit changes  </span>
</span></span><span class="line"><span class="cl">git commit -m <span class="s1">&#39;commit message&#39;</span>
</span></span><span class="line"><span class="cl">
</span></span><span class="line"><span class="cl"><span class="c1"># push changes to branch  </span>
</span></span><span class="line"><span class="cl">git push origin branch-name
</span></span><span class="line"><span class="cl">
</span></span><span class="line"><span class="cl"><span class="c1"># next pull request/merge with master on github or command line  </span></span></span></code></pre></div></div>
<p>Sometimes you don&rsquo;t want to track some files(like local env configuration
settings)</p>]]></description></item></channel></rss>