Databases
StackOverflow2013
Postsdbo
PORails Capistrano deploy_to path
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORails Capistrano deploy_to path
    primarykey
    data
    text
    <p>I'm trying to deploy my rails app, until now hostet at Heroku, now at DigitalOcean using Capistrano. I've created a "1-Click-Rails-Application", which creates a blank rails app, so when I open the remote server in my webbrowser, the typical rails welcome screen (index.html) shows up. When I ssh to the remote directory, the path to the rails app is:</p> <pre><code>/home/rails/ </code></pre> <p>inside of the rails directory are the typical rails folders like controllers etc. So I thought that the correct deploy_to path should be:</p> <pre><code>set :deploy_to, "/home/rails/" </code></pre> <p>I've seen so many different directory suggestions that I really can't figure out what could be right. I had </p> <pre><code>set :deploy_to, "var/www/#{application}" </code></pre> <p>as well, which didn't seem to work either.</p> <p>I'm glad I've managed to upload my local app to the new vpn server without any errors at all. I want to avoid using a git repo to save the extra costs for a private git repo and push it directly from my computer. The problem is, after a </p> <pre><code>cap production deploy:cold </code></pre> <p>which does a lot and runs through without any errors, doesn't seem to upload anything. At least I can't find any of "my" files on the server. Well, I'm really happy that I got this far but don't understand why my config isn't working. I hope someone can help. Here is my deploy.rb from the config directory. (I'm using rvm.)</p> <pre><code>require 'capistrano/ext/multistage' require "bundler/capistrano" require "rvm/capistrano" set :application, "myApp" set :user, "root" set :port, 22 set :deploy_to, "home/rails/" set :repository, "." set :scm, :none set :deploy_via, :copy set :checkout, :export set :use_sudo, false #set :rvm_ruby_string, "ruby-2.0.0p195@#{application}" set :rvm_type, :user set :rvm_type, :system server "xx.xxx.xx.xx", :app, :web, :db, :primary =&gt; true after "deploy", "deploy:migrate" </code></pre> <p>I'm using Rails 3.2.13 and Ruby 2.0.0. Thanks a lot!</p> <p><strong>Update:</strong> I was originally following a railscast capistrano deployment tutorial to get my head around this. Thus I created the deploy folder inside the config folder with a production.rb and a staging.rb inside.</p> <p>Long story short, I've found "my" rails app, inside a var/www/xx.xxx.xx.xx/current/ directory on the server. The path is specified inside the production.rb which looks like this:</p> <pre><code>server "xx.xxx.xx.xx", :app, :web, :db, :primary =&gt; true set :deploy_to, "/var/www/xx.xxx.xx.xx" </code></pre> <p>I could now change the path above to /home/rails but the actual rails app was inside the additional folder named current. How do I have to write the path so that there is no current directory? at least not there?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USLinus
    1. USLinus
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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