My NAS a “MyBook World Edition™ from  WesternDigital®” was sitting in the background just keeping the back-ups from time to time. Over the holiday period I took the time to setup and integrate the network drive better with Ubuntu and try to use the drive with subversion which I failed some time ago and did not bother to look any closer into it.

So here is what helped me (some of it is rather trivial).

As always this is without any warranty, try this at your own risk!

Ubuntu integration

For the integration with Ubuntu you just have to install an nfs package as shown below

[bash gutter=”false”]sudo apt-get install nfs-common[/bash]

Then you have to change the fstab file in an editor with root privileges by executing:

[bash gutter=”false”]sudo gedit /etc/fstab[/bash]

In this file you have to add for each of your partitions of your NAS a line. An example is given below, which works for me. You have to change the following to adapt it to your situatin.

  1. You should assign to your NAS a fixed IP
  2. The fixed IP has to go where in the example below you have the 192….100 address
  3. The path on the NAS drive follows the fixed IP address
  4. After some spaces you have to enter where on your Ubuntu machine the partitions are mounted

[code]# NAS Drive      /media/georg    nfs  defaults,user      0       0     /media/backup   nfs  defaults           0       0     /media/public   nfs  defaults,user      0       0[/code]

SVN integration

With the plain integration shown above SVN will not work properly. The nasty point is here that if you put your repository to the NAS you can check-out a working directory. But once you have made changes and want to commit you fail with an error that tells you that subversion was not able to get a lock on the file …db/txn-current-lock.

This can be worked around by adding to the fstab file options additional entries. For the previous example a change for a partition would look as given in the example below.

[code]# NAS Drive           /media/georg    nfs  defaults,user,nolock,bg      0       0

A side effect will be probably (I am not 100% sure here) that in such an environment you should better not work with more than one person on the repository as otherwise you may get conflicts if 2 or more try to commit at the same point in time.

Installing Rails Version 2.3.11

I have just recently re-installed rails, mysql and mongrel in an older version 2.3.11 and its required libraries and tools on 3 computers. As not all instructions I found in the web did work for me here is my learned procedure to get up and running on Linux Ubuntu 12.04.

Installing ruby

[bash]sudo apt-get install ruby rubygems[/bash]

To get access to the ruby documentation and to enable “./script/console” you have to install ri and interactive ruby.

[bash]sudo apt-get install ri irb[/bash]

Installing rails

As Rails version 3 caused some problems for me and some of my aps are not yet ported to Rails 3, I explicitly installed v2.3.8.

[bash]sudo gem install rails -v 2.3.11 -V[/bash]

I prefer to use the verbose option “-V” as the installation is sometimes just sitting around seemingly not responding anymore. In verbose mode however after a few seconds you should see what URLs are queried. So give it some time and be patient.

Installing MySQL

[bash]sudo apt-get install mysql-server mysql-client
sudo apt-get install libmysql-ruby libmysqlclient-dev
sudo apt-get install ruby1.8-dev
sudo gem install mysql [/bash]

Preparing the environment

Ok, the previous steps installed some gems but the executables are not yet accessible. So we have to add their path to our shell.

For this we first check where the binaries were installed, just call:

[bash]gem env[/bash]

Which provides the following output on my computer.

[bash]RubyGems Environment:
– RUBY VERSION: 1.8.7 (2009-06-12 patchlevel 174) [i486-linux]
– INSTALLATION DIRECTORY: /var/lib/gems/1.8
– RUBY EXECUTABLE: /usr/bin/ruby1.8
– EXECUTABLE DIRECTORY: /var/lib/gems/1.8/bin
– ruby
– x86-linux
– /var/lib/gems/1.8
– /home/georg/.gem/ruby/1.8
– :update_sources => true
– :verbose => true
– :benchmark => false
– :backtrace => false
– :bulk_threshold => 1000
– [/bash]

We then take the executable path and add it to our shells path.

[bash]cd ~
gedit .bashrc [/bash]

And in the just opened editor we add the following lines and save the file again.

[bash]# Ruby environment
export PATH=${PATH}:/var/lib/gems/1.8/bin [/bash]

Calling the “which” command should then produce the following output, given your gems path is identical to mine.

[bash]which ruby gem rails rake mongrel_rails

Remaining is now the installation of helpful tools and helpers such as the mongrel application server, SSL- or the debugging support.

[bash]sudo gem install mongrel ruby-debug log4r
sudo apt-get install libopenssl-ruby[/bash]