<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Sysops on Jose Castrillo</title>
    <link>https://jose.castrillo.eu/tags/sysops/</link>
    <description>Recent content in Sysops on Jose Castrillo</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Sun, 04 Feb 2024 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://jose.castrillo.eu/tags/sysops/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Faster and simple maintenance page</title>
      <link>https://jose.castrillo.eu/post/maintenance-page/</link>
      <pubDate>Sun, 04 Feb 2024 00:00:00 +0000</pubDate>
      <guid>https://jose.castrillo.eu/post/maintenance-page/</guid>
      <description>&lt;p&gt;Working on different platform either to update, patch, etc need to be notificate for those people that consume that services, it shouldn&amp;rsquo;t change if that service it&amp;rsquo;s internal, you must notificate your teams about it.&lt;/p&gt;
&lt;p&gt;When you&amp;rsquo;re into your maintenance window you can use a faster way to broadcast everyone you&amp;rsquo;re working on it; I use this simple solution when I was working into a Jenkins migration, hence I stop the jenkins service and instead of 500 html error I developed a simple html text exposing it by a nginx container by the root path.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
