pl  |  en

Ruby on Rails

Also read the Platform changes (MT 1.0 vs 2.0) article that contains the information unrelated to the specific type of an application.

Virtual environment

The applications installed through autoinstallation have a RVM configured and they also have their own gemset. After you enter the application catalogue in the shell, there should be the specific Ruby version and the application gemset automatically set up.

MT 1.0 you didn’t have to use a virtual environment, and it was causing many gem compatibility problems among the applications.


All the applications are launched by the unicorn. At this moment, there is no possibility to set a number of the application processes through the panel. Although, if necessary, we will implement such a tool. Please send your submissions to

The number of processes can be increased through the unicorn built-in mechanisms.

kill -SIGTTIN PID_mastera

Will work until the application is restarted.

Launching mode

You can set the application mode in the panel, and not as it has been done in the past through the shell RAILS_ENV variable.

Note: Setting the mode will not cause the shell RAILS_ENV to change. After the operations in shell (like rake db:migrate) it will be necessary to set the RAILS_ENV manually.

RAILS_ENV=production rake db:migrate

Environment variables

You can set up any environment variable in the .environment file in the application catalogue. These settings are being loaded when the application starts, yet, they’re not being loaded in the shell.


The application installed through the panel (adding an application with the “create on the server” option checked) has a automatically configured database. The configuration is done by the environment.

In the conf/database.yml file there is a piece of our code that is loading the access data. You can keep this file in the repo, publish it without concern that the database will leak out, and also you can change the password through the panel without updating the application config.

You can also configure the database normally. In that case, you will have to replace our code from the database.yml file with your own database access data.

Git repository

When you set up the application through the panel, also a git repository will be automatically created. The push for this repo will cause that the application catalogue will be updated and the application will be restarted.

Supported versions

You can launch the Rails 4.0.0/3.2 or 1.9.3/2.0.0 application through the panel. You can install any version of Ruby and Rails through the RVM.