Readme setup steps for Ubuntu

I've been running through it on Ubuntu 14.04 just fine, but the steps are a bit different, and I am unsure how best to document, mostly due to the postgres commands not being exposed by default.

For starters, you aren't going to get redis with the default apt repos. But can easily do the following:

wget http://download.redis.io/releases/redis-2.8.13.tar.gz
tar xzf redis-2.8.13.tar.gz
cd redis-2.8.13
make
sudo make install

Next you can grab postgres and phantomjs from the repos:

sudo apt-get install postgresql libpq-dev phantomjs

And lastly, you need to expose postgres and initdb in /usr/bin

cd /usr/bin
sudo ln -s ../share/postgresql-common/pg_wrapper postgres
sudo ln -s ../share/postgresql-common/pg_wrapper initdb

pg_wrapper is a utility that calls it's link name in the /usr/lib/postgresql/VERSION/bin directory, and while ubuntu sets up some of them, it doesn't setup the two being used in the Makefile.

Thanks for creating this issue @twk3 !

Regarding redis, what about the redis-server package? http://packages.ubuntu.com/trusty/misc/redis-server

Considering Debian/Ubuntu likes turning services on by default, we might have to tell Ubuntu users to delete the redis: line from their Procfile after running make so they can just use their system redis.

About Postgres: what about invoking make as make PATH=/usr/lib/postgresql/VERSION/bin:$PATH and doing an extra hack with sed when rendering the Procfile, so that the correct full path to the posgres executable ends up in the Procfile?

The Postgres tweak I suggested would have a smaller footprint on your development machine.

Not sure how I missed the redis-server package. I just tried it out and it works fine running in standalone mode while the redis-server service is still running. So at least the setup/install isn't broken.

Your postgres approach sounds good, at which point our install instructions for Ubuntu are still pretty small.

I lied, the default redis is on the same port. Doesn't appear to care while booting up. But will likely cause unexpected problems when using it.

For postgres, if brew also installs pg_config, we could run pg_config --bindir to get the directory

for using pg_config --bindir, it seems to work on OS X too and I think it is just what we need.

Regarding Redis and ports, I expect either the system redis or the Procfile redis to abort during startup because only one of them can grab the port. Until GitLab properly supports Redis sockets users would have to choose between system redis and Procfile redis. Deleting the redis: line from the Procfile means choosing the system redis.

mentioned in merge request !9 (merged)

Working on updating the README. Planning to Update the Debian section, and add a Ubuntu section. Wanted some early feedback because the PhantomJS seems to be an additional headache on debian wheezy.

Ubuntu

sudo apt-get install postgresql libpq-dev phantomjs redis-server libicu-dev cmake

Debian

sudo apt-get install postgresql libpq-dev redis-server libicu-dev cmake libfreetype6 libfreetype6-dev libfontconfig1
cd ~
wget https://bitbucket.org/ariya/phantomjs/downloads/phantomjs-1.9.7-linux-$(uname -m).tar.bz2
sudo tar xvjf phantomjs-1.9.7-linux-$(uname -m).tar.bz2 -C /usr/local/share
sudo ln -s /usr/local/share/phantomjs-1.9.7-linux-$(uname -m)/bin/phantomjs /usr/local/bin/phantomjs

On Debian I saw that the version of Redis errored out when trying to bind to the same port. Which is what we were expecteing. Kinda interesting that the newer redis-server on Ubuntu 14.04 doesn't error out. (I've confirmed that it also isn't reachable on the port though, only on it's unix socket)

Either way, we will have to add a note about having to choose between the service and the standalone.

Sounds great @twk3 . Consider submitting a MR just for Ubuntu to get started; that would help a lot of people already.

mentioned in merge request !12 (merged)

Status changed to closed

!14 (merged) Fixes the redis issue, closing this issue