Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p><strong>What build of Linux is most recommended for this configuration?</strong></p> <p>Any of the distributions will work fine as long as they can run Apache2 (which is almost all of them) and you can install Passenger (along with ruby and rails). I personally use CentOS and find its package manger to be ridiculously easy to use (<a href="http://yum.baseurl.org/" rel="nofollow noreferrer">yum</a>).</p> <pre><code>yum install -y httpd ruby gem install rails passenger </code></pre> <p>Then all you have to do is a little configuration in <code>/etc/httpd/conf/httpd.conf</code> to add Passenger (following the install file for Passenger <code>passenger-install-apache2-module</code>) and point it to your deployment folder <code>.../app_name/current/public</code>.</p> <p>Since you are using Passenger you should override the restart task to work for it.</p> <p><code>config/deploy.rb</code></p> <pre><code>namespace :deploy do desc "Restart Application" task :restart, :roles =&gt; :app do run "touch #{current_path}/tmp/restart.txt" end end </code></pre> <p><strong>How do I set up Capistrano on my server for remote deployment?</strong></p> <p>All Capistrano needs is SSH access with sufficient permissions to deploy, migrate, restart app server, etc. Just follow the <a href="http://www.capify.org/getting-started" rel="nofollow noreferrer">getting started guide</a> at the <a href="http://www.capify.org/" rel="nofollow noreferrer">Capistrano website</a> and you will be up and running in no time.</p> <p>Capistrano needs access to your SCM, you will need to allow it to connect to your machine. All Capistrano does is checkout your code into a release folder and moves the symbolic link from the old version and restarts your app server.</p> <p><strong>What is the biggest snag you watch for when deploying from a localhost development, to deployment on a totally different OS?</strong></p> <p>The biggest snag is with migrations, test, test, test, and test them some more. A bug in your application is easy to fix and redeploy, but a bug in your migration could end up a huge pain in the ass with the possibility of data loss.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload