QA Site

updating (and downgrading) Ruby on QA Site

spikef2163i5 — Sun, 10 Aug 2008 16:33:27 -0400

I’m updating to Ruby 1.8.6 on the Fluffy QA Site. It’s operational CentOS 5 final. (cat /etc/redhat-release) I added the following yum repository: [ruby] name=ruby baseurl=http://repo.premiumhelp.eu/ruby/ gpgcheck=0 enabled=0 Then I ran: yum –enablerepo=ruby install ruby ruby-devel rubygems ruby-docs ruby-ri ruby-irb ruby-rdoc I don’t know the quality of this repository, so don’t take it as my endorsement. I found it on the internet via google which turned up this suggestion on a mailing list. Most likely the Ruby version supplied by doing an rpm update on the official Centos 5 repository would’ve been fine, Ruby 1.8.5-5.el5_2.3 – note, I’m actually going back to to the official Ruby installation because of the fact that there's a security vulnerability here: http://www.securitytracker.com/alerts/2008/Jul/1020476.html Rather than rip it out by the roots as well as installing the correct RPMs by force, I found a cool package: yum-allowdowngrade: yum list available ruby* Loading “allowdowngrade” plugin Loading “installonlyn” plugin Setting up repositories Reading repository metadata in from local files Available Packages ruby.i386 1.8.5-5.el5_2.3 updates ruby-devel.i386 1.8.5-5.el5_2.3 updates ruby-docs.i386 1.8.5-5.el5_2.3 updates ruby-irb.i386 1.8.5-5.el5_2.3 updates ruby-libs.i386 1.8.5-5.el5_2.3 updates ruby-mode.i386 1.8.5-5.el5_2.3 updates ruby-rdoc.i386 1.8.5-5.el5_2.3 updates ruby-ri.i386 1.8.5-5.el5_2.3 updates ruby-tcltk.i386 1.8.5-5.el5_2.3 updates yum grouplist yum groupremove “Ruby” yum “groupinstall “Ruby” yum remove ruby-libs ruby-docs yum install ruby-libs ruby-docs yum install ruby-irb ruby-rdoc ruby-ri so now my ruby installation looks like: Installed Packages ruby.i386 1.8.5-5.el5_2.3 installed ruby-devel.i386 1.8.5-5.el5_2.3 installed ruby-docs.i386 1.8.5-5.el5_2.3 installed ruby-irb.i386 1.8.5-5.el5_2.3 installed ruby-libs.i386 1.8.5-5.el5_2.3 installed ruby-mode.i386 1.8.5-5.el5_2.3 installed ruby-rdoc.i386 1.8.5-5.el5_2.3 installed ruby-ri.i386 1.8.5-5.el5_2.3 installed The reason I wanted to upgrade to 1.8.6 was to get the 1.9 warnings, as well as to retain consistent with windows. I’ll still utilize 1.86 on Linux VMs not facing the internet, but not on QA Sites. rubygems 1.1.1 was installed by hand.

Ruby environment on behalf of QA Site

spikef2163i5 — Sun, 10 Aug 2008 19:00:27 -0400

As noted on the previous post, I’m sticking with Ruby 1.8.5 fo QA Sites until I get a convincing argument to upgrade manually — meaning a custom compile. I should really learn how to build RPMs. Ruby 1.8.5-5.el5_2.3 official CentOS 5 rpm: yum install ruby ruby-devel ruby-irb ruby-ri ruby-libs ruby-docs ruby-rdoc RubyGems 1.1.1 manual install: wget http://rubyforge.org/frs/download.php/35283/rubygems-1.1.1.tgz tar -xvzf rubygems-1.1.1.tgz cd rubygems-1.1.1 ruby setup.rb Rails 2.0.2 gem install rails -v=2.0.2 Rake 0.8.1 installed with Rails Rspec 1.1.4 gem install rspec ZenTest 3.10.0 gem install ZenTest test-unit 2.0.2 gem install test-unit Capistrano 2.4.3 gem install capistrano MySQL 5.0 database version 5.0.45-7.el5*: yum install mysql mysql-devel mysql-server ruby mysql drivers version 2.7: gem install mysql — –with-mysql-lib=/usr/lib/mysql/ –with-myse=/usr/include/mysql/ PostgreSQL 8.1 database version 8.1.11-1.el5_1.1: yum install postgresql postgresql-devel postgresql-server postgresql-libs ruby drivers 0.7.9.2008.03.18: gem install pg I had trouble installing databases drivers on Windows using the older postgres drivers helped, but I think I had to specify the directory: gem install postgres SQLite 3.6.1 yum install sqlite sqlite-devel (3.3.6-2) gem install sqlite3-ruby Windows needs the SQLite dll as well as the exe. They require to both be in the PATH environment variable. # gem list –local *** LOCAL GEMS *** actionmailer (2.0.2) actionpack (2.0.2) activerecord (2.0.2) activeresource (2.0.2) activesupport (2.0.2) hoe (1.7.0) mysql (2.7) pg (0.7.9.2008.03.18) rails (2.0.2) rake (0.8.1) rspec (1.1.4) rubyforge (1.0.0) sqlite3-ruby (1.2.2) test-unit (2.0.0) ZenTest (3.10.0)

Linode Installation

spikef2163i5 — Tue, 09 Sep 2008 21:49:13 -0400

QA-Site.com is on a Linode with 360MB RAM as well as 15GM Disk using the Linode Xen-beta. I pointed the qa-site.com domain registrar to user Linode’s nameservers: NS1.LINODE.COM NS2.LINODE.COM The last couple of days have been spent installing software in order to set up. I still have some CPAN work (for bugzilla) as well as Python work (for trac) but once that’s ready I’ll take a snapshot as a base OS. I tried to utilize RPMs on behalf of everything (except MagickWand, as noted below) but I might in the future desire to have a custom Apache + mod_perl + mod_ssl + mod_python + PHP as well as MySQL/PostgreSQL on behalf of each qa-site. That way install is just a copy & unzip. I would prefer everything to be tidily installed in /usr/local instead of RPMs with config files, init scripts, etc. scattered all over. But one of the advantages of the RPMs is the existing init scripts on behalf of things like service httpd start. One thing I would require to do is remove the gcc dependencies, so I don’t have to add as well as remove it. First, I removed the root login from /etc/ssh/sshd_config Second, I did a complete ‘yum update’ from the CentOS 5 base repository. Then I installed the web as well as database RPMs (using yum mostly) Here is a list of what I’ve installed via yum: http-2.2.3-11-el5 mod_ssl-2.2.3-11.el5.centos perl-5.8.8-10.el5_0.2 php-5.1.6-15.el5 Ruby-1.8.5-5 ruby-ri ruby-rdoc ruby-irb ruby-docs a bunch of perl libraries (whatever I needed from default RPMs) a bunch of php/pear/pecl libraries (whatever I needed from default RPMSs) mysql-5.0.22-2.2.el5_1.1, mysql-server-5.0.22-2.2.el5_1.1 mod_auth_mysql subversion-1.4.2-2.el5 subversion-perl, subversion-ruby, mod_dav_svn OpenLDAP-2.3.27-8 php-LDAP, perl-LDAP, python-LDAP, mod_authz_ldap FreeRADIUS-1.1.3-1.2.el5 ImageMagick-6.2.8 ImageMagick-perl-6.2.8 ImageMagick-devel-6.2.8 gd-devel-2.0.33-9.3.fc6 For packages from utterramblings, I created the following file: etc/yum.repos.d/utterramblings.repo name=Jason’s Utter Ramblings Repo baseurl=http://www.jasonlitka.com/media/EL$releasever/$basearch/ enabled=1 gpgcheck=1 gpgkey=http://www.jasonlitka.com/media/RPM-GPG-KEY-jlitka And upgraded/installed the following from utterramblings.repo: php- 5.2.5 php-xcache mysql-5.0.54, , mysql-server-5.0.54

More installation fun with ImageMagick

spikef2163i5 — Tue, 09 Sep 2008 23:04:33 -0400

When I installed ImageMagick from source to install MagickWand, I broke the perl Image::Magick install. So that the bugzilla checksetup.pl script broke on the check with the error message: perl: symbol lookup error: /usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi/auto/Image/Magick/Magick.so: undefined symbol: MagickCoreGenesis So I needed to back out the manual ImageMagick build, or perl would be broken. If that meant losing MagickWand, so be it. A search on behalf of “how to uninstall perl modules” revealed some idiotic feedback on the perl.beginners newsgroups to the effect that you’d never desire to uninstall a perl module. I originally attributed it to Randall Schwartz (author of Learning Perl), but in fact, though he was in the conversation, he only made technical clarification. When an atrocious system like CPAN is your installer (or when you’re using anything that uses autoconf) you WILL desire to uninstall something at some point. Eventually, I decided the only solution I had was to jog ‘make install’ again on the ImageMagick source distribution as well as see what it installed. After a lot of analysis, it turned out to not be as bad as I thought. I only had to remove two files: # rm -r /usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi/Image/Magick* # rm -r /usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi/auto/Image/Magick* and edit perllocal.pod I found a lovely script to clean up perllocal at perlmonks: http://www.perlmonks.org/?node_id=483020 I then pruned the remaining Image::Magick sections from perllocal.pod as well as reinstalled the ImageMagick-perl-6.2.8 RPM. I haven’t thoroughly tested it yet, but I trust both PerlMagick as well as MagickWand are still working, though I still have the two versions of ImageMagick. I also removed the ImageMagick-devel-6.2.8 RPM.

Bugzilla dependencies

spikef2163i5 — Sat, 13 Sep 2008 22:29:27 -0400

I installed bugzilla at the end of fixing the ImageMagick stuff this morning. This wasn’t quite straightforward either, but I’d waded through this before with one-shore as well as a local install on windows as well as a CentOS VMWare image. Here are my notes: – download bugziila 3.0.3 # wget http://ftp.mozilla.org/pub/mozilla.org/webtools/bugzilla-3.0.3.tar.gz – unzip bugzilla # tar -xvzf bugzilla-3.0.3.tar.gz – transfer bugzilla to site # mv bugzilla-3.0.3 /var/www/bugzilla – restart websever # service httpd configtest # service httpd restart – check bugzilla dependencies # cd /var/www/bugzilla # perl checksetup.pl – install dependencies via CPAN cpan Bundle::CPAN cpan Bundle::Bugzilla – this failed on the DBD::mysql 4.0 plugin (3.0 should have workd on behalf of Bugzilla 3.0.3, though 4.0 is required on behalf of Bugzilla 3.1.x) I fixed that with a manual install of the CPAN module as well as temporarily setting the root password to “” to match what was expected in the test script. Alternately, you can specify the default username & password to test with (somewhere). After this, the basics were installed, but I got the extras with: # cpan Email::Send # cpan Email::MIME:Modifier # cpan Template::Plugin::GD # cpan SOAP::Lite # cpan HTML::Scrubber # cpan Email::MIME::Attachment::Stripper # cpan Email::Reply I had to manually install chart: – manually install Chart # wget http://search.cpan.org/CPAN/authors/id/C/CH/CHARTGRP/Chart-2.4.1.tar.gz # tar -xvzf Chart-2.4.1.tar.gz # cd Chart-2.4.1 # perl Makefile.PL # manufacture && manufacture test && manufacture install – create bugzilla account on mysql #mysql -u root -p mysql>grant all on bugzilla.* to ‘bugzilla’@'localhost’ identified by ‘********’; – edit bugzilla localconfig # vi ./localconfig $db_driver = ‘mysql’; $db_host = ‘localhost’; $db_name = ‘bugzilla’; $db_user = ‘bugzilla’; $db_pass = ‘********’; – install Bugzilla by operational checksetup.pl again # perl checksetup.pl After this, it was just some playing with Apache to eliminate the 404 Forbidden (I’ll probably forget what I did again) as well as then configure via the admin login. I had a brief problem with cookies because of the fact that I tried to set the cookie domain — that shall take some more work with mulitple installs, but apart from the qa-site.com as well as demo.qa-site.com being hosted together, it won’t be a problem with VPSes.

Subversion

spikef2163i5 — Sun, 14 Sep 2008 22:50:42 -0400

Apart from being used as a developer repository, subversion is used by Trac. Subversion installation was pretty straightforward. I installed the RPMs with yum: # yum install subversion mod_dav_svn –Optionally install bindings on behalf of languages # yum install subversion-perl subversion-ruby subversion-java – create a repository # svnadmin create /var/www/svn/repository-name – edit httpd.conf (the RPM creates /etc/httpd/conf.d/subversion.conf) LoadModule dav_svn_module modules/mod_dav_svn.so LoadModule authz_svn_module modules/mod_authz_svn.so – create a location Options Indexes Order allow,deny Allow from all DAV svn SVNParentPath /var/www/svn AuthType Basic AuthName “Subversion Login” AuthUserFile /var/www/access/.htpasswd Require valid-user – restart apache Note on behalf of all you rocketscientists who utilize the SVNParentPath directive: http://localhost/svn returns 404 Forbidded. Navigate to http://localhost/svn/respository-name works. Set up svn to utilize HTTPS optionally.

Trac setup

spikef2163i5 — Sun, 14 Sep 2008 22:20:16 -0400

Make sure apache, python, mod_python, subversion, sqlite, clearsilver, & clearsilver-python are installed as well as working first. Trac uses the swig bindings installed with Subversion, not pysvn. – install setuptools on behalf of genshi as well as pygments (needed on behalf of 0.11, not on behalf of 0.10) # wget http://peak.telecommunity.com/dist/ez_setup.py # python ez_setup.py # easy_install genshi # easy_install pygments # easy_install docutis – optionally install silvercity on behalf of syntax highlighting # wget http://ufpr.dl.sourceforge.net/sourceforge/silvercity/SilverCity-0.9.7.tar.gz # tar -xvzf SilverCity-0.9.7.tar.gz # python setup.py install – Download, unzip, install trac: # wget ftp://ftp.edgewall.com/pub/trac/trac-0.10.4.tar.gz # tar -xvzf trac-0.10.4.tar.gz # python ./setup.py install — Create a project: # trac-admin /var/www/trac-site initenv – edit trac.ini (no changes yet) – test with build in server # tracd –port 8000 /var/www/trac-site – configure apache to point to trac site SetHandler mod_python PythonInterpreter main_interpreter PythonHandler trac.web.modpython_frontend PythonOption TracEnv /var/www//trac-site PythonOption TracUriRoot /trac The trac documentation is actually pretty good as well as this closely follows it. http://trac.edgewall.org/wiki/0.10/TracInstall http://trac.edgewall.org/wiki/TracModPython I did have some trouble with getting python as well as subversion working combined on windows, however (that may have had to do with python-2.4, I don’t think I tried downgrading to 2.3, as well as It might have had trouble with newer Apache 2.2.4) And fast-cgi isn’t an option on windows.

New mailserver: exim + dovecot

spikef2163i5 — Sun, 14 Sep 2008 19:07:58 -0400

I set up exim + dovecot on behalf of qa-site. I’m pretty happy with the results so far. Installation was a snap, as well as configuration was practically pain free (thanks in part to google as well as this mini howto on behalf of SMTP auth.) I created SSL keys on behalf of both exim as well as dovecot (that are practically identical) using this command: openssl req -x509 -newkey rsa:1024 -keyout exim.key -out exim.crt -days 365 -nodes openssl req -x509 -newkey rsa:1024 -keyout dovecot.key -out dovecot.crt -days 365 -nodes and then edited the configuration files to point to them: exim.conf: tls_certificate = /usr/share/ssl/certs/exim.crt tls_privatekey = /usr/share/ssl/private/exim.key dovecot.conf: ssl_cert_file = /usr/share/ssl/certs/dovecot.crt ssl_key_file = /usr/share/ssl/private/dovecot.key in exim.conf, I also made the following changes: primary_hostname = qa-site.com #this would have used `uname -n` by default uncommented: auth_advertise_hosts = ${if eq {$tls_cipher}{}{}{*}} and commented: #auth_advertise_hosts = and then added: plain: driver = plaintext public_name = PLAIN server_prompts = : server_set_id = $2 server_condition = “${if pam{$2:$3}{1}{0}}” login: driver = plaintext public_name = LOGIN server_prompts = “Username:: : Password::” server_set_id = $1 server_condition = “${if pam{$1:$2}{1}{0}}” in addition, to utilize maidir, I edited exim.conf to include: local_delivery: driver = appendfile # file = /var/mail/$local_part delivery_date_add envelope_to_add return_path_add group = mail mode = 0660 maildir_format = true directory = /home/${local_part}/Maildir create_directory = true check_string = “” escape_string = “” in dovecot, I just had to set: mail_location = maildir:~/Maildir I created a .muttrc file to read my Maildir: set mbox_type=Maildir set folder=”~/Maildir” set mask=”!^\.[^.]“ set mbox=”~/Maildir” set record=”+.Sent” set postponed=”+.Drafts” set spoolfile=”~/Maildir” I now have working TLS with SMTP auth, POP3 as well as IMAP access through remote thundirbird/outlook as well as local mutt clients. They both utilize PAM system-auth by default (exim needed read access to /etc/shadow.) The next steps are to set up procmail to utilize spamassassin as well as clamav to filter incoming mail, as well as set up a webmail client. I mentioned on my spikef2163i5 blog that I’m looking on behalf of webmail application recommendations. I’m leaning towards v-webmail. One last thing shall be to set up virtual domains, so that, on behalf of example, cuencatravel.qa-site.com can have it’s posses email setup.