<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: TheCommieAxolotl</title>
    <description>The latest articles on DEV Community by TheCommieAxolotl (@thecommieaxolotl).</description>
    <link>https://dev.to/thecommieaxolotl</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1067112%2F00918743-f79c-419e-acff-e19b7868b3f7.png</url>
      <title>DEV Community: TheCommieAxolotl</title>
      <link>https://dev.to/thecommieaxolotl</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/thecommieaxolotl"/>
    <language>en</language>
    <item>
      <title>Introducing OnlyNv</title>
      <dc:creator>TheCommieAxolotl</dc:creator>
      <pubDate>Tue, 15 Apr 2025 22:23:18 +0000</pubDate>
      <link>https://dev.to/thecommieaxolotl/introducing-onlynv-4141</link>
      <guid>https://dev.to/thecommieaxolotl/introducing-onlynv-4141</guid>
      <description>&lt;p&gt;Today, I am pleased to introduce &lt;strong&gt;OnlyNv&lt;/strong&gt;, a platform for peer-to-peer and peer-to-CI&lt;sup id="fnref1"&gt;1&lt;/sup&gt; syncing of environment variables and secrets.&lt;/p&gt;

&lt;p&gt;OnlyNv allows you to take your local &lt;code&gt;.env&lt;/code&gt; files, and store them in a centralised location. This allows you to share your environment variables with your team, and keep them in sync across all your CI/CD pipelines.&lt;/p&gt;

&lt;h2&gt;
  
  
  How it works
&lt;/h2&gt;

&lt;p&gt;OnlyNv stores your environment variables in a centralised, encrypted database.&lt;/p&gt;

&lt;p&gt;Whenever you add or update an environment variable, OnlyNv will automatically sync it with your CI/CD pipelines.&lt;br&gt;
Furthermore, your team members can pull the latest environment variables directly to their local machines.&lt;/p&gt;
&lt;h2&gt;
  
  
  Demo
&lt;/h2&gt;

&lt;p&gt;Let's say we have a project, &lt;code&gt;my-project&lt;/code&gt;, with the following &lt;code&gt;.env&lt;/code&gt; file:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;DB_HOST=localhost
DB_USER=root
DB_PASS=password
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;We also have a GitHub repository, &lt;code&gt;my-org/my-project&lt;/code&gt;, which we want to setup to receive our environment variables.&lt;/p&gt;

&lt;p&gt;First, we need to create a new project on OnlyNv. We can do this by running the following command in our terminal:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nv"&gt;$ &lt;/span&gt;nv init
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This will redirect us to the OnlyNv dashboard, where we can create a new project.&lt;/p&gt;

&lt;p&gt;We'll now have a new file in our project directory, &lt;code&gt;.lnvrc&lt;/code&gt;, which tells the CLI how to sync our environment variables.&lt;/p&gt;

&lt;p&gt;We can now use &lt;code&gt;nv link&lt;/code&gt; to log in to OnlyNv and sync our environment variables with our CI/CD pipelines.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nv"&gt;$ &lt;/span&gt;nv &lt;span class="nb"&gt;link
  &lt;/span&gt;Linking project...

  Press ENTER to open &lt;span class="k"&gt;in &lt;/span&gt;browser:
  https://onlynv.dev/projects/...
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This will open a browser window, where we can log in to OnlyNv and link the project.&lt;/p&gt;

&lt;p&gt;Finally, we can use &lt;code&gt;nv sync&lt;/code&gt; to sync our environment variables with the server, and any CI/CD pipelines linked to our project.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nv"&gt;$ &lt;/span&gt;nv &lt;span class="nb"&gt;sync
  &lt;/span&gt;Syncing my-platform &lt;span class="o"&gt;(&lt;/span&gt;...&lt;span class="o"&gt;)&lt;/span&gt;

  ✔ Found 1 file
    .env

  ✔ Encrypted data

  ✔ Sent data

  ✔ Decrypted data from server
  Writing .env
  Synced project

  Updated GitHub repository: https://github.com/my-org/my-project
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;p&gt;OnlyNv is currently in beta, and we are looking for feedback from the community. If you want to try it out please join the &lt;a href="https://onlynv.dev/login" rel="noopener noreferrer"&gt;waitlist&lt;/a&gt;, and feel free to upvote on &lt;a href="https://www.producthunt.com/products/onlynv" rel="noopener noreferrer"&gt;ProductHunt&lt;/a&gt; to show your support.&lt;/p&gt;

&lt;p&gt;Happy coding!&lt;/p&gt;




&lt;ol&gt;

&lt;li id="fn1"&gt;
&lt;p&gt;Currently, we offer Vercel, GitHub, Netlify, and GitLab support. More platforms are coming soon. ↩&lt;/p&gt;
&lt;/li&gt;

&lt;/ol&gt;

</description>
      <category>programming</category>
      <category>opensource</category>
      <category>startup</category>
    </item>
    <item>
      <title>A New Look for git.rela.dev</title>
      <dc:creator>TheCommieAxolotl</dc:creator>
      <pubDate>Tue, 12 Dec 2023 02:15:26 +0000</pubDate>
      <link>https://dev.to/thecommieaxolotl/a-new-look-for-gitreladev-1l34</link>
      <guid>https://dev.to/thecommieaxolotl/a-new-look-for-gitreladev-1l34</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;Brought over from &lt;a href="https://rela.dev/blog/new-look-git-rela-dev"&gt;the Rela blog&lt;/a&gt;.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;As of this week, &lt;a href="https://git.rela.dev"&gt;the RelaGit site&lt;/a&gt; has been overhauled with a totally new appearance.&lt;br&gt;
The old style of the site was a bit too homogeneous, and it was decided that it lacked some of the elegance and confident design that was wanted to convey.&lt;/p&gt;

&lt;p&gt;As you can see &lt;a href="https://git-rela-dpsmegyab-tcm-collaborate.vercel.app/"&gt;in this old deployment&lt;/a&gt;, the old landing page lacked both the brand identity and confidence. But let's break down the hero section:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;em&gt;The Navigation Bar:&lt;/em&gt; There's only one way to phrase it, weak. It lacks a strong gap between items and therefore feels cramped, it is also always at full white, which makes interactions feel uninteresting and not considered. In the new design, the bar sits back from the screen, taking more space but feeling less intrusive because of the dimmed colors and the more considered spacing.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;em&gt;The Hero Text:&lt;/em&gt; Sites that have their product name as their hero text don't convert well. The too-dim subtitle also didn't help, it looked like an afterthought. In the new design, the hero text is a description of the client, and the subtitle is baked into the hero. I've also scrapped the call to action button in favour of a linear design, with intuitive call to actions later down in the page.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;em&gt;The Image:&lt;/em&gt; The one thing that remained mostly the same is the image, it's still a simple photo of the client, although I've updated the diff that is shown in the screen to give a more complete view of the client's look.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;Along with the obvious changes, I also replaced the disabled download button with a waitlist signup field. By entering your email, you will be added to the waitlist for the client, and you will be notified when it is ready for beta testing.&lt;/p&gt;

&lt;h2&gt;
  
  
  Continued Development of the client
&lt;/h2&gt;

&lt;p&gt;Don't worry, this hasn't stopped development on the client, this month alone has seen the below changes:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;There's now an integrated branch picker, which dynamically responds to any changes made remotely or locally and simplifies the many commands that can be used to interact with branches.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Logical a11y flow has been improved throughout the app, with the simplification of settings, auto-focusing of dynamic elements, and the integration of more focus traps.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The app now has a proper onboarding process, with a beautiful first-open screen, and a multi-step, hands-on tutorial that guides you through the app's most common features.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--Au_3P6T9--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_800/https://rela.dev/uploads/4.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--Au_3P6T9--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_800/https://rela.dev/uploads/4.png" alt="The new branch picker, with a branch being created." width="800" height="495"&gt;&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;That's all for now, check out the &lt;a href="https://git.rela.dev"&gt;new site&lt;/a&gt; today, and sign up for the waitlist!&lt;/p&gt;

&lt;p&gt;Au revoir! 👋&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>programming</category>
      <category>git</category>
      <category>design</category>
    </item>
    <item>
      <title>8 Months and Counting.</title>
      <dc:creator>TheCommieAxolotl</dc:creator>
      <pubDate>Sun, 24 Sep 2023 09:25:16 +0000</pubDate>
      <link>https://dev.to/thecommieaxolotl/8-months-and-counting-1kco</link>
      <guid>https://dev.to/thecommieaxolotl/8-months-and-counting-1kco</guid>
      <description>&lt;p&gt;Brought over from &lt;a href="https://rela.dev/blog/8-months-counting"&gt;Rela&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;In tech, the hardest commodity to keep is motivation.  Sure, if you're sponsored by a massive company or salaried at a FAANG, you can keep going as long as you like. But for an independent, developing things on the side, it's a lot harder.&lt;/p&gt;

&lt;p&gt;I made that my last blog post in the honeymoon phase of the project. &lt;br&gt;
I was excited, I was motivated, and I was ready to go. &lt;br&gt;
I had a plan, I had a vision, and I had a goal. &lt;br&gt;
I was going to make something that I could be proud of, and that people would love to use.&lt;/p&gt;

&lt;p&gt;And then I started &lt;em&gt;really&lt;/em&gt; working on it.&lt;/p&gt;

&lt;p&gt;Turns out, building a git client from the ground up is &lt;em&gt;hard&lt;/em&gt;. There are countless features to implement and using something with such a temperamental API is a nightmare. So, I lost my motivation... for about 4 months.&lt;/p&gt;

&lt;h3&gt;
  
  
  The 4 Month Hiatus
&lt;/h3&gt;

&lt;p&gt;After a while of doing other things, tinkering with some fun ideas (à la &lt;a href="https://github.com/TheCommieAxolotl/pyotr"&gt;pyotr&lt;/a&gt;), I had some thoughts about Rela(Git) again. I started by implementing &lt;a href="https://npmjs.com/package/@relagit/commits"&gt;a simple CLI tool for the commit standard&lt;/a&gt;, and then I started working on the client again.&lt;/p&gt;

&lt;h3&gt;
  
  
  What's with the new look?
&lt;/h3&gt;

&lt;p&gt;During the Hiatus, I came up with a design system that I call Illyrica &lt;em&gt;(ih-lyr-i-cah)&lt;/em&gt;, after a technologically advanced planet in a certain Sci-Fi series.&lt;br&gt;
Quickly, I ported RelaGit to use this new design system, and I'm really happy with the results.&lt;/p&gt;

&lt;p&gt;Head over to the &lt;a href="https://rela.dev/blog/8-months-counting#whats-with-the-new-look"&gt;main blog post&lt;/a&gt; to see the difference.&lt;/p&gt;

&lt;h3&gt;
  
  
  What's really next?
&lt;/h3&gt;

&lt;p&gt;I know I said this last time, but I'm going to try and keep this blog updated more often, as well as posting to [here].&lt;/p&gt;

&lt;p&gt;But for now, cya!&lt;/p&gt;

</description>
      <category>programming</category>
      <category>git</category>
      <category>relagit</category>
    </item>
    <item>
      <title>Announcing RelaGit</title>
      <dc:creator>TheCommieAxolotl</dc:creator>
      <pubDate>Fri, 21 Apr 2023 03:36:40 +0000</pubDate>
      <link>https://dev.to/thecommieaxolotl/announcing-relagit-2i2j</link>
      <guid>https://dev.to/thecommieaxolotl/announcing-relagit-2i2j</guid>
      <description>&lt;p&gt;Brought over from &lt;a href="https://rela.dev/blog/announcing-relagit"&gt;Rela&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Today, I am pleased to announce our first product, RelaGit. RelaGit is a Git Client designed to do everything &lt;em&gt;you&lt;/em&gt; need, and everything &lt;em&gt;you&lt;/em&gt; want. The client provides a simple, intuitive javascript API for managing workflows, repositories, and more.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why RelaGit?
&lt;/h2&gt;

&lt;p&gt;Existing Git Clients are well-tested, and have been around for a long time. They are battle-hardened but unfortunately, they are also very complex. RelaGit is meant to be simple, and easy to use. RelaGit is built with TypeScript, Electron, SolidJS and a custom Git library. Thsi will allow it to be faster and more speialised in what it does best. The client is designed to be useful for what the modern developer does ona day-to-day basis and make tasks faster and easier.&lt;/p&gt;

&lt;h2&gt;
  
  
  Open Source???
&lt;/h2&gt;

&lt;p&gt;At Rela, we believe in the values of Open Source. (We even have a whole &lt;a href="https://rela.dev/oss"&gt;pledge&lt;/a&gt; on the topic) We are committed to making good Open Source software, and as such, we will be making RelaGit open source under the MIT license when it's release date comes around. For now, it is closed source. You can follow the development of RelaGit on our &lt;a href="https://github.com/RelaGit"&gt;GitHub&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  What's next?
&lt;/h2&gt;

&lt;p&gt;This has been brief but don't worry: more is coming soon. Keep a look out for more posts on the blog, and more information added to the site.&lt;/p&gt;

</description>
      <category>git</category>
      <category>typescript</category>
      <category>news</category>
      <category>solidjs</category>
    </item>
  </channel>
</rss>
