StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
18164272
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2013-08-10T16:57:59.740
FavoriteCount
0
LastActivityDate
2013-08-10T16:57:59.740
LastEditDate
2017-05-23T12:10:36.807
LastEditorUserId
-1
OwnerUserId
0
ParentId
14159689
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
I answered this on a question I made myself here: <a href="https://stackoverflow.com/questions/18134046/multiple-rails-4-app-using-nginx-unicorn/18161635#18161635">Multiple Rails 4 app using nginx + unicorn</a> But here's a answer: I'm using Ruby 2.0 and Rails 4.0. I suppose you already have nginx and unicorn installed. So, let's get started! In you nginx.conf file we are going to make nginx point to a unicorn socket: <pre><code>upstream unicorn_socket_for_myapp { server unix:/home/coffeencoke/apps/myapp/current/tmp/sockets/unicorn.sock fail_timeout=0; } </code></pre> Then, with your server listening to port 80, add a location block that points to the subdirectory your rails app is (this code, must be inside server block): <pre><code>location /myapp/ { try_files $uri @unicorn_proxy; } location @unicorn_proxy { proxy_pass http://unix:/home/coffeencoke/apps/myapp/current/tmp/sockets/unicorn.sock; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header Host $http_host; proxy_redirect off; proxy_set_header X-Forwarded-Proto $scheme; } </code></pre> Now you can just Unicorn as a Deamon: <pre><code>sudo unicorn_rails -c config/unicorn.rb -D </code></pre> The last thing to do, and the one I dug the most is to add a scope for your rails routes file, like this: <pre><code>MyApp::Application.routes.draw do scope '/myapp' do root :to => 'welcome#home' # other routes are always inside this block # ... end end </code></pre> This way, your app will map a link /myapp/welcome, intead of just /welcome <h2>But there's a even better way</h2> Well, the above will work on production server, but what about development? Are you going to develop normally then on deployment you change your rails config? For every single app? That's not needed. So, you need to create a new module that we are going to put at <code>lib/route_scoper.rb</code>: <pre><code>require 'rails/application' module RouteScoper def self.root Rails.application.config.root_directory rescue NameError '/' end end </code></pre> After that, in your <code>routes.rb</code> do this: <pre><code>require_relative '../lib/route_scoper' MyApp::Application.routes.draw do scope RouteScoper.root do root :to => 'welcome#home' # other routes are always inside this block # ... end end </code></pre> What we are doing is to see if the root directory is specified, if so use it, otherwise, got to "/". Now we just need to point the root directory on config/enviroments/production.rb: <pre><code>MyApp::Application.configure do # Contains configurations for the production environment # ... # Serve the application at /myapp config.root_directory = '/myapp' end </code></pre> In config/enviroments/development.rb I do not specify the config.root_directory. This way it uses the normal url root.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POmultiple rails apps on nginx and unicorn
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. This table or related slice is empty.
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
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.