Vesta CP: Installing Ruby and Python Web Applications

Hi Habr.

I love when everything is in its place, everything is clean and tidy.
Therefore, once a quarter, raking creative mess.

For me it is important to have a stable OS with the confidence that after the next daily update, nothing will break. Many developers choose the OS based on the availability of current versions of software. I can cook Centos and in " yum-y install yum-cron " I am 99.98% sure.

I'll tell you how you can use the latest versions of ruby ​​and python for web development. Also according to the results, 4 web applications from one regular user will be installed on the server: djangocms (python 3.4.3), quokka (python 2.7.9), redmine (ruby 2.2.1), refinerycms (ruby 2.0.0). No attention will be paid to subtle application launch parameters (database selection, number of verker, connections, logs, etc.). I wanted to describe LocomotiveCMS, but it turned out to be a locomotive with a bunch of manual edits for the setup.
')
For comfort and convenience we will use the control panel VestaCP. Because she is simply gorgeous and ideologically dear.

System preparation

So, we have a test VPS with Centos 6, root access. Contrary to the official manual, we will put a panel with the option "-d".

curl -O http://vestacp.com/pub/vst-install.sh bash vst-install.sh -d 

Thus, we will limit the installation only to the "epel" repository, without the "remi" (i.e. without the latest versions of mysql and php).
Add domain templates for nginx:


Further installation of packages: mongodb for quokka, supervisor of the third branch, and dev-packages:


And the last thing required from root is the supervisor setting:


That's all that is required from the super user.

We add a user (reguser) to Vesta, enable SSH Access in bash and create 4 domains:
djangocms.test.site , quokka.test.site , redmine.test.site , refinerycms.test.site .
In the settings of each domain, we specify the previously added nginx profile called “socket”.
Thus, nginx will listen to unix-sockets that will be created by the supervisor, with regular user rights.

On the pages of each domain, the unpleasant “502 Bad Gateway” will be displayed, which means we are on the right path.

Customization of the user environment

If in the "system" we have everything neatly, then in the "hamster" we will have many, many self-collection garbage.
However, we will not see anything. For us, all the dirty work will be done by PyEnv and RbEnv.

 su - reguser 

First decide the issue RbEnv. The significant page of rbenv.org will send us to the githab, where we are independently aware of the shims philosophy.

 git clone https://github.com/sstephenson/rbenv.git ~/.rbenv echo 'export PATH="$HOME/.rbenv/bin:$PATH"' >> ~/.bash_profile echo 'eval "$(rbenv init -)"' >> ~/.bash_profile . ~/.bash_profile type rbenv git clone https://github.com/sstephenson/ruby-build.git ~/.rbenv/plugins/ruby-build 

We look at the available versions and collect the latest versions of the branches 2.0 and 2.2:

 rbenv install -l rbenv install 2.0.0-p643 rbenv install 2.2.1 

Oddly enough, but PyEnv is a fork of RbEnv, more here . We do almost the same thing:

 curl -L https://raw.githubusercontent.com/yyuu/pyenv-installer/master/bin/pyenv-installer | bash echo 'export PATH="$HOME/.pyenv/bin:$PATH" eval "$(pyenv init -)" eval "$(pyenv virtualenv-init -)"' >> ~/.bash_profile . ~/.bash_profile pyenv install -l pyenv install 2.7.9 pyenv install 3.4.3 

Install Redmine

You must first create a mysql database in Vesta:

 cd ~/web/redmine.test.site/public_html rm -rf * hg clone --updaterev 3.0-stable https://bitbucket.org/redmine/redmine-all . echo 'production: adapter: mysql2 database: reguser_redmine host: localhost username: reguser_redmine password: "password" encoding: utf8 ' > config/database.yml 

Next, a very important line, it creates a .ruby-version file in the current directory, thereby indicating the desired version of shims. The same thing happens with python versions with pyenv local xxx .

 rbenv local 2.2.1 gem install bundler bundle install --without development test rake generate_secret_token RAILS_ENV=production rake db:migrate RAILS_ENV=production rake redmine:load_default_data 

The choice of thin or unicorn (as indicated in the supervisor):

 gem install thin echo 'gem "thin"' >> Gemfile gem install unicorn echo 'gem "unicorn"' >> Gemfile 

The first went. It remains to distort the supervisor from the console ' supervisorctl restart redmine.test.site ', or through the web the muzzle ... and the redmine is ready for work redmine.test.site :

RefineryCMS installation

All the same, taking into account the official manual:

 cd ~/web/refinerycms.test.site/public_html/ rbenv local 2.0.0-p643 gem install rails --version 4.1.8 gem install execjs rails new . -m http://refinerycms.com/t/edge gem install unicorn 

A page inviting you to create an admin is waiting for refinerycms.test.site/refinery :

Installing DjangoCMS

 cd ~/web/djangocms.test.site/public_html pyenv local 3.4.3 pip install djangocms-installer 

A dialogue will follow. Choose “Languages” = “en, ru”, “Twitter Theme” = “yes”, “with examples” = “yes”. The rest is the default.

 djangocms -p . project 

Upon completion, they will be asked to provide a login password and postal address.

 python manage.py cms check # check cms pip install gunicorn 

And here it is djangocms.test.site :

QUOKKA installation

 cd ~/web/quokka.test.site/public_html git clone https://github.com/quokkaproject/quokka . pyenv local 2.7.9 pip install -r requirements.txt sed -i "s|^GRAVATAR.*$|&\n 'use_ssl': True,|" quokka/settings.py python manage.py populate python manage.py createsuperuser ln -s quokka/static static pip install gunicorn 

And here is the last beast quokka.test.site :



It is worth noting that, unlike RbEnv / RVM, in PyEnv you can create virtualenv. These things are not mutually exclusive.
I hope my guide with the installation of various web applications was interesting.

Thank.