The script is fine with me.

Perhaps split it up into master script and dependants for ruby, rvm, rails, specific project setup, extra libraries?

Then we can edit only those dependant scripts if needed, and add more scripts to master script for something new.
Maybe move the whole setup to rake?

And give everyone a task/script to write - phantomJs and dependencies, postgre, automation tools, etc., and assign them as maintainers?

Craig tested this script on Ubunty 14.04 Trusty and reports that because does not configure Postgres permissions, db:setup etc will not work.

A couple of ways to tackle this. Either create a superuser in your name:

[0:12] Paul McCulloch: I was looking at some of the install scripts to help me figure out pg install and found this allowed no mod of pg_hba.conf:
`sudo -u postgres createuser --superuser paul` 

[7:08] David Corking: http://www.postgresql.org/docs/9.1/static/app-createuser.html

or

edit pg_hba.conf as we do in the LocalSupport and vagrant scripts (thanks to @tansaku )

# needs work to handle variable white space
#
sudo sed -i -e 's/local\s\+all\s\+postgres\s\+peer/local all postgres peer map=basic/g' /etc/postgresql/9.1/main/pg_hba.conf

Which approach shall we choose?

We got the following note added to the WSO wiki from @freeranger (I think) following our install instructions:

Note: On OSX El Capitan and above, you may get this error:

An error occurred while installing eventmachine (1.0.7), and Bundler cannot continue.
Make sure that `gem install eventmachine -v '1.0.7'` succeeds before bundling.

If you then try to install that gem, it also fails like this: eventmachine/eventmachine#643, which is because OpenSSL is no longer distributed with OSX so you may need to use brew to set it up:

brew link openssl --force

Then re-try the rails_setup.sh line above and you should be good to go on to the next step.

Assuming that we think that maintaining this script is something that makes sense for us then perhaps we should update and fix this issue in the setup script itself ...

Perhaps we should be recommending people to use C9 - @dalupus - I wonder if this script (with some fixes) set to autorun when someone created a c9 instance would be what we want in terms of a C9 "template" AgileVentures/WebsiteOne#807