<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:media="http://search.yahoo.com/mrss/"><channel><title><![CDATA[Notes to myself]]></title><description><![CDATA[Thoughts, stories and ideas.]]></description><link>https://jenslukas.com/</link><image><url>https://jenslukas.com/favicon.png</url><title>Notes to myself</title><link>https://jenslukas.com/</link></image><generator>Ghost 5.22</generator><lastBuildDate>Wed, 06 May 2026 10:27:36 GMT</lastBuildDate><atom:link href="https://jenslukas.com/rss/" rel="self" type="application/rss+xml"/><ttl>60</ttl><item><title><![CDATA[Use different SSH Key for Github Deployment]]></title><description><![CDATA[<p>A problem I recently experienced was, that I wanted to use a different SSH Key for cloning my repositories on production.</p><blockquote>Background: I would like to use a different key (read-only) on my servers. A nice solution on Github is to set specific Deployment keys to checkout repositories for example</blockquote>]]></description><link>https://jenslukas.com/use-different-ssh-key-for-github-deployment/</link><guid isPermaLink="false">5f7c29c12e95f331b3482cb1</guid><category><![CDATA[Github]]></category><category><![CDATA[Deployment]]></category><category><![CDATA[SSH]]></category><dc:creator><![CDATA[Jens Lukas]]></dc:creator><pubDate>Tue, 06 Oct 2020 08:36:27 GMT</pubDate><content:encoded><![CDATA[<p>A problem I recently experienced was, that I wanted to use a different SSH Key for cloning my repositories on production.</p><blockquote>Background: I would like to use a different key (read-only) on my servers. A nice solution on Github is to set specific Deployment keys to checkout repositories for example on the production server. (<a href="https://docs.github.com/en/free-pro-team@latest/developers/overview/managing-deploy-keys#deploy-keys">https://docs.github.com/en/free-pro-team@latest/developers/overview/managing-deploy-keys#deploy-keys</a>)</blockquote><p>Steps:</p><p>1) Create a new SSH Key Pair on the machine you would later on like to read the repository. The command is as simple as `ssh-keygen`. Don&apos;t use the default path, as this would overwrite your existing one. I also did not add a passphrase.</p><p>2) Open and edit ~/.ssh/config. In my case, the file did not exist yet. Add the following content to the file:</p><pre><code class="language-sh">Host github.com
  IdentityFile ~/.ssh/github_rsa</code></pre><p>Adjust the path to the one set in step 1.</p><p>3) Add the public key on your Github repository (Settings -&gt; Deploy keys)</p><p>Done :)</p>]]></content:encoded></item><item><title><![CDATA[Welcome to jenslukas.com]]></title><description><![CDATA[Welcome, it's great to have you here.
We know that first impressions are important, so we've populated your new site with some initial getting started posts that will help you get familiar with everything in no time.]]></description><link>https://jenslukas.com/welcome/</link><guid isPermaLink="false">5f6485db0e3b501c211eb77a</guid><category><![CDATA[Getting Started]]></category><dc:creator><![CDATA[Ghost]]></dc:creator><pubDate>Fri, 18 Sep 2020 10:03:12 GMT</pubDate><media:content url="https://static.ghost.org/v3.0.0/images/welcome-to-ghost.png" medium="image"/><content:encoded><![CDATA[<h2 id="about-me"><strong>About me</strong></h2><img src="https://static.ghost.org/v3.0.0/images/welcome-to-ghost.png" alt="Welcome to jenslukas.com"><p>Too lazy for now, so just stalk me on XING or LinkedIn :)</p><h2 id="what-s-about-to-happen-here">What&apos;s about to happen here?</h2><p>There are tasks and problems with which I am confronted regularly, but in very large time intervals. Unfortunately, I almost always start at 0 again when solving the problem and need to start over my research again.</p><p>I have been planning it for a long time and now finally realized, I want to write down these topics so that I can work through them faster next time. But I thought, why not just write them down in public, maybe it helps someone.</p><p>I won&apos;t write big tutorials here, gonna ignore the context most of the time and won&apos;t be offering big explanations, but maybe it will still provide some added value.</p><p>Due to my job, this will be mainly about tech topics, but who knows what else might come :)</p>]]></content:encoded></item><item><title><![CDATA[Setting up a local mySQL instance with Docker on Mac]]></title><description><![CDATA[<!--kg-card-begin: markdown--><p>I whitewashed my Macbook a while ago and spend it a fresh and clean installation. It almost took me 3 month to recognize that I was missing a local mySQL instance for development. Dreadful that it took so long to recognize, need to find more time for coding.</p>
<p>However, a</p>]]></description><link>https://jenslukas.com/setting-up-a-local-mysql-instance-with-docker-on-mac/</link><guid isPermaLink="false">5f64c1ae2e95f331b3482ca8</guid><dc:creator><![CDATA[Jens Lukas]]></dc:creator><pubDate>Fri, 18 Sep 2020 09:14:24 GMT</pubDate><content:encoded><![CDATA[<!--kg-card-begin: markdown--><p>I whitewashed my Macbook a while ago and spend it a fresh and clean installation. It almost took me 3 month to recognize that I was missing a local mySQL instance for development. Dreadful that it took so long to recognize, need to find more time for coding.</p>
<p>However, a quick guide to get a mySQL instance, accessible from my local machine, up and running with Docker.</p>
<ol>
<li>
<p>Install Docker Desktop (<a href="https://docs.docker.com/docker-for-mac/">https://docs.docker.com/docker-for-mac/</a>)</p>
</li>
<li>
<p>Start Docker Desktop and login with your Docker ID (or created a new one)</p>
</li>
<li>
<p>optional: I reduced the Resources to just use one CPU and 1GB of memory. This can be done in the Docker Desktop settings. I don&apos;t run any heavy DB tasks on my local machine and prefer to keep resources free for other stuff.</p>
</li>
<li>
<p>Check out which version of MySQL server you would like to run: <a href="https://hub.docker.com//mysql">https://hub.docker.com//mysql</a>. I went with 5.7 as this is the same version we use in production.</p>
</li>
<li>
<p>Open up terminal session and enter the following command (adjust the version behind : to match your favored version):<br>
<code>docker pull mysql/mysql-server:5.7</code></p>
</li>
<li>
<p>Check if it installed correctly executing  <code>docker images</code><br>
<img src="https://jenslukas.com/content/images/2020/09/Screenshot-2020-09-17-at-14.50.50.png" alt="Screenshot-2020-09-17-at-14.50.50" loading="lazy"></p>
</li>
<li>
<p>Now let&apos;s run this machine.<br>
<code>docker run -d --publish=3307:3306 --name=mysql-instance -e MYSQL_ROOT_PASSWORD=root mysql/mysql-server:5.7</code></p>
</li>
</ol>
<p>Once again, you need to adjust the command to match your version.<br>
I also changed the port from 3306 to 3307, just in case it might already be in use. If you prefer, just go with the standard 3306:3306. By adjusting the port, you could run as many instances as you want. As you might have already guessed I set the password for our root user, just to root.</p>
<ol start="8">
<li>Finally we need to grant our root user the right to connect externally (actually from our local machine). You should not go the following way with a production system, but I am just lazy and would like to have the root user being able to connect. A more secure way would be to create a new user with limited permissions.</li>
</ol>
<p>Connect to MySQL from the terminal using following command (adjust mysql-instance, if you chose a different name in Step 7):<br>
<code>docker exec -it mysql-instance mysql -u root -p</code></p>
<p>Now let&apos;s allow root user to connect from any host:<br>
<code>update mysql.user set host=&apos;%&apos; where host=&apos;localhost&apos; and user=&apos;root&apos;;</code></p>
<p>and flush privileges:<br>
<code>flush privileges;</code></p>
<p>Now we&apos;re done and can use our instance.</p>
<!--kg-card-end: markdown-->]]></content:encoded></item></channel></rss>