<?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>Forem: idanlodzki</title>
    <description>The latest articles on Forem by idanlodzki (@idanlodzki).</description>
    <link>https://forem.com/idanlodzki</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%2F3471873%2F61974987-4255-4f1a-bcb7-9b570e78f141.png</url>
      <title>Forem: idanlodzki</title>
      <link>https://forem.com/idanlodzki</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/idanlodzki"/>
    <language>en</language>
    <item>
      <title>Early-stage open-source project: OpsiMate</title>
      <dc:creator>idanlodzki</dc:creator>
      <pubDate>Wed, 03 Sep 2025 21:14:43 +0000</pubDate>
      <link>https://forem.com/idanlodzki/early-stage-open-source-project-opsimate-llc</link>
      <guid>https://forem.com/idanlodzki/early-stage-open-source-project-opsimate-llc</guid>
      <description>&lt;p&gt;Hey folks, me and a couple of friends have been working on a side project called &lt;strong&gt;OpsiMate&lt;/strong&gt;.&lt;br&gt;&lt;br&gt;
The idea is one simple tool to manage servers, Docker hosts, and Kubernetes clusters in a single place.  &lt;/p&gt;

&lt;p&gt;We want it to be easy to use even for non-technical people - the idea came from a real need to give sales teams or NOC staff a simple way to handle tasks.&lt;br&gt;&lt;br&gt;
Right now it can do basics like restarting Docker, and later we’d like to support more advanced actions such as triggering Jenkins jobs.  &lt;/p&gt;

&lt;p&gt;We’d love any suggestions, thoughts, or tips - and of course code contributions are more than welcome (we also have a Slack if you’d like to join).  &lt;/p&gt;

&lt;p&gt;On top of that, if you have experience with licensing, we’d really appreciate hearing your perspective on our choice of &lt;strong&gt;AGPL&lt;/strong&gt; - both where it worked well and where it caused adoption issues.  &lt;/p&gt;

&lt;p&gt;Repo: &lt;a href="https://github.com/OpsiMate/OpsiMate" rel="noopener noreferrer"&gt;https://github.com/OpsiMate/OpsiMate&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fgh2jkmml6cugslsigliz.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fgh2jkmml6cugslsigliz.png" alt=" " width="800" height="311"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fcv000ym6k5iwe0yf8owc.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fcv000ym6k5iwe0yf8owc.png" alt=" " width="800" height="385"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
      <category>opensource</category>
      <category>monitoring</category>
      <category>devops</category>
    </item>
  </channel>
</rss>
