CirrusGrid PaaS provides Ruby application servers based on the two software stacks:
Herewith, both ones are configured to utilize the Passenger application server by default, which is integrated via the appropriate custom module. Moreover, if needed, the NGINX Ruby stack can be easily configured to work with the different inbuilt servers:
Let’s see how it can be switched on the NGINX Ruby server.
The Passenger module is used for all newly created Ruby environments by default. Follow the next steps to change to the different one:
1. Click the Config button next to your NGINX Ruby application server.
2. Within the opened configuration file manager panel, navigate to the /etc/nginx/nginx.conf file. Find the include app_servers strings:
3. Uncomment the string with the required module and comment the previously active one.
Note: Only one string for the application server module should be active, otherwise you’ll get the compatibility errors.
For example, we’ll switch to Puma.
4. Save the changes and Restart Nodes of the NGINX application server to apply them.
5. Access your node via SSH (e.g. using Web SHH) and run the selected module with the appropriate command executed from the project directory:
pumactl -F config/puma.rb --pidfile puma.pid -S puma.state start &
Note: For the Unicorn application server run the unicorn_rails -c config/unicorn.rb -D & command instead.
Note: If you would like to switch to the different module, it could be done in the same way, but you need to stop the currently running application server:
That’s all! Now you can work with the chosen Ruby NGINX module.
Powered by BetterDocs
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.