A lot of provisions done by me need to be automated, since each install process can take 2 hours to get every single step done according to standards. I could set up scripts to do enviroment settings or to do install and configurations, but to be honest, that is not really elegant, and the question remains, how would the scripts be copied/mounted to the servers, and what process would start them.
Continue reading “Debian Squeeze Recipe + LDAP + Mail Relay”
During vhost provisions with LDAP auth I was seeing errors:
root@test:~# /etc/init.d/apache2 restart
Syntax error on line 30 of /etc/apache2/sites-enabled/000-default:
AuthBasicProvider not allowed here
Action 'configtest' failed.
The Apache error log may have more information.
Continue reading “AuthBasicProvider not allowed here”
Default setup of nagios on on of our systems had .htaccess auth method setup, and with growing number of users we needed to change to a more centralized and manageable auth method. We decided to include Nagios into our LDAP infrastructure and let Apache web server do the most of the work.
Continue reading “Nagios3 frontend with ldap auth”
After installing puppet I was researching a possibility to secure puppet dashboard with either ldap auth or apache htpasswd auth. Some quick tests and I got a working config set up fairly easily.
Continue reading “Puppet-dashboard with LDAP Auth on Debian Squeeze”
I had some time and started playing around with puppet. At first I was really frustrated with some sites giving documentation or guides that had errors that resulted in hours of debuging, and googling. So I would like to present my short but tested guide.
Continue reading “Puppet install on Debian Squeeze with Dashboard”
During the weekend while installing Redmine I had a big error with gems, it was missing Postgre libs and headers. I was thinking about excluding it from its gem files, but decided to solve the problem and let it have the header files needed for bundle install:
Continue reading “Rubygems PG missing error in debian squeeze”
One of the other errors I see frequently during ruby install is:
An error occured while installing rmagick (2.13.1), and Bundler cannot continue.
Make sure that `gem install rmagick -v '2.13.1'` succeeds before bundling.
The issue can be solved easily.
apt-get install libmagick++-dev libmagickcore-dev libmagickwand-dev
It will install alot of dependent packages, but all required headers will be present. In my opinion magick is a little to resource heavy, and should be a little less hungry.