<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>DevOps on Dejan Bosanac</title>
    <link>/categories/devops/</link>
    <description>Recent content in DevOps on Dejan Bosanac</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    
    <lastBuildDate>Tue, 27 Nov 2007 00:00:00 +0000</lastBuildDate><atom:link href="/categories/devops/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Multiple Apache instances on Gentoo box</title>
      <link>/posts/2007-11-27-multiple-apache-instances-on-gentoo-box/</link>
      <pubDate>Tue, 27 Nov 2007 00:00:00 +0000</pubDate>
      
      <guid>/posts/2007-11-27-multiple-apache-instances-on-gentoo-box/</guid>
      <description>&lt;p&gt;I&amp;rsquo;ve started looking how to enable both PHP4 and PHP5 on our (relatively) new dev box running &lt;a href=&#34;http://www.gentoo.org/&#34;  target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;Gentoo&lt;/a&gt;. The box is already running PHP4 so the task was to add PHP5 support as well.&lt;/p&gt;&#xA;&lt;p&gt;The official &lt;a href=&#34;http://www.gentoo.org/proj/en/php/php4-php5-configuration.xml&#34;  target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;guide&lt;/a&gt; is rich in options you can use to achieve this. I didn&amp;rsquo;t want any CGI since we use PHP vhost configurations extensively and I didn&amp;rsquo;t want to deal with suPHP as well. Since it is a dev box, it is totally OK to have two instances with similar configurations running on two different ports. Unfortunately, it is the part of the official docs that is not as complete as other parts and not working as advertised. So, here&amp;rsquo;s a mental note (for me) and perhaps a few hour saver for others.&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>CVS, CentOS and SELinux</title>
      <link>/posts/2007-11-02-cvs-centos-and-selinux/</link>
      <pubDate>Fri, 02 Nov 2007 00:00:00 +0000</pubDate>
      
      <guid>/posts/2007-11-02-cvs-centos-and-selinux/</guid>
      <description>&lt;p&gt;I was migrating a CVS repository from one server to another today and ran on the interesting issue. I was getting a &amp;ldquo;Permission denied&amp;rdquo; error on the &lt;code&gt;CVSROOT/config&lt;/code&gt; file no matter what privileges were set. It turns out that problem is with SELinux on CentOS, so the easiest solution is to just turn it off.&lt;/p&gt;&#xA;&lt;p&gt;/usr/sbin/setenforce 0&lt;/p&gt;&#xA;&lt;p&gt;If you want to be sure that it will be turned off after the server restart, just edit the &lt;code&gt;/etc/sysconfig/selinux&lt;/code&gt; file and set &lt;code&gt;SELINUX&lt;/code&gt; to &lt;code&gt;permissive&lt;/code&gt;&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>Changing CVS Root from shell</title>
      <link>/posts/2007-05-24-changing-cvs-root-from-shell/</link>
      <pubDate>Thu, 24 May 2007 00:00:00 +0000</pubDate>
      
      <guid>/posts/2007-05-24-changing-cvs-root-from-shell/</guid>
      <description>&lt;p&gt;Here&amp;rsquo;s a simple script that recursively changes &lt;code&gt;CVS/Root&lt;/code&gt; files in the project tree&lt;/p&gt;&#xA;&lt;div class=&#34;highlight-wrapper&#34;&gt;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; class=&#34;chroma&#34;&gt;&lt;code class=&#34;language-text&#34; data-lang=&#34;text&#34;&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;find . -name Root -exec sh -c &amp;#39;echo :pserver:example@cvs.example.com:2401/var/cvsroot &#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;&amp;gt; {}&amp;#39; \;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/div&gt;&#xA;&lt;p&gt;Note &lt;code&gt;sh -c&lt;/code&gt; segment of &lt;code&gt;-exec&lt;/code&gt; switch, which is necessary in order to successfully redirect to appropriate files.&lt;/p&gt;&#xA;&lt;p&gt;This could be useful for updating deployed projects with the repository that has moved (for any reason).&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
