https://www.mkaramuk.dev/Recent content on Muhammed Karamuk - Software Developer - Personal BlogHugoen-usTue, 09 Jul 2024 00:00:00 +0000https://www.mkaramuk.dev/posts/creating-container-image-registry/Tue, 09 Jul 2024 00:00:00 +0000https://www.mkaramuk.dev/posts/creating-container-image-registry/<p>Hi there,</p> <p>Sometimes you may need to create your own container image registry, either running on your local machine or on cloud/on-prem, where you manage it by yourself. Examples for use cases:</p> <ul> <li>The images owned by your organization are high in size and take longer to upload to remote locations,</li> <li>Access control over the images,</li> <li>Image encryption,</li> <li>Requirement to upload images to remote registry during the development process,</li> </ul> <h1 id="what-is-container-image-registry">What is Container Image Registry?</h1> <p>Container images basically exists in two places; your local machine and remote image registries.</p>https://www.mkaramuk.dev/posts/dotenvx-new-generation-dotenv-tool/Wed, 03 Jul 2024 00:00:00 +0000https://www.mkaramuk.dev/posts/dotenvx-new-generation-dotenv-tool/<p>Hello there,</p> <p>In this article, we will take a look at <a href="https://dotenvx.com/">dotenvx</a> which is created by the developer behind <a href="https://github.com/motdotla/dotenv">dotenv</a>, <a href="https://github.com/motdotla">@motdotla</a>.</p> <h2 id="what-was-dotenv">What was dotenv?</h2> <p>As you all know, we configure the programs we write to use environment variables to determine how they should work. To avoid having to redefine these environment variables every time we run the program, we use <em>.env</em> files.</p> <p>Basically, the logic behind of the <em>.env</em> files is very simple; read the <em>.env</em> file on the path (by default in the process working directory) and make the variables defined in it available to our program as environment variables. This way, when we want to run our program, we don&rsquo;t have to define the variables we need one by one.</p>