<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Ocs on Aperture Zone</title>
    <link>https://aperturezone.com/tags/ocs/</link>
    <description>Recent content in Ocs on Aperture Zone</description>
    <image>
      <url>https://aperturezone.com/logo.webp</url>
      <link>https://aperturezone.com/logo.webp</link>
    </image>
    <generator>Hugo -- gohugo.io</generator>
    <language>fr-fr</language>
    <lastBuildDate>Thu, 09 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://aperturezone.com/tags/ocs/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>OCS Inventory NG - What the doc doesn&#39;t say</title>
      <link>https://aperturezone.com/posts/ocs-inventory/</link>
      <pubDate>Thu, 09 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/ocs-inventory/</guid>
      <description>&lt;h2 id=&#34;the-project&#34;&gt;The Project&lt;/h2&gt;
&lt;p&gt;The initial idea was simple: deploy &lt;strong&gt;OCS Inventory NG&lt;/strong&gt; to centralize the hardware and software inventory of the infrastructure. A server, agents, a web console. Nothing too complicated.&lt;/p&gt;
&lt;p&gt;Spoiler: I thought it would be a piece of cake, but it turned out to be a real headache.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&#34;act-1--server-installation-or-quotperl-is-your-enemyquot&#34;&gt;Act 1 — Server Installation, or &amp;quot;Perl Is Your Enemy&amp;quot;&lt;/h2&gt;
&lt;p&gt;Installing OCS on the server side involves a &lt;code&gt;setup.sh&lt;/code&gt; script that asks questions. Lots of questions. And it expects precise answers—pressing Enter without thinking is a recipe for disaster.&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
