StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POApache2 multiple name-based virtual hosts on one machine with rails/rack
primarykey
Id
16547547
data
AcceptedAnswerId
16560400
AnswerCount
1
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-05-14T15:47:07.347
FavoriteCount
1
LastActivityDate
2013-05-15T08:37:17.887
LastEditDate
LastEditorUserId
0
OwnerUserId
266297
ParentId
0
PostTypeId
1
Score
0
ViewCount
2624
LastEditorDisplayName
text
Body
Am stuck on configuring apache to serve up two different sites with Name based virtual hosts at: <pre><code>http://experimental/ </code></pre> and <pre><code>http://api.experimental/ </code></pre> On one machine this setup works fine, and apache reports this: <pre><code>apachectl -D DUMP_VHOSTS apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName VirtualHost configuration: wildcard NameVirtualHosts and _default_ servers: *:* is a NameVirtualHost default server experimental (/etc/apache2/sites-enabled/00-nowa.conf:3) port * namevhost experimental (/etc/apache2/sites-enabled/00-nowa.conf:3) port * namevhost api.experimental (/etc/apache2/sites-enabled/00-nowa.conf:15) Syntax OK </code></pre> On the 2nd machine this does not work, both URLS end up pointing to the first app, it's output of the same command is which has additional : lines: <pre><code>apachectl -D DUMP_VHOSTS apache2: apr_sockaddr_info_get() failed for experimental apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName [Tue May 14 15:36:08 2013] [warn] NameVirtualHost *:80 has no VirtualHosts [Tue May 14 15:36:08 2013] [warn] NameVirtualHost *:80 has no VirtualHosts VirtualHost configuration: wildcard NameVirtualHosts and _default_ servers: *:* experimental (/etc/apache2/sites-enabled/00-nowa.conf:3) *:* api.experimental (/etc/apache2/sites-enabled/00-nowa.conf:15) Syntax OK </code></pre> The vhost files for each machine are this for the broken one: <pre><code><VirtualHost *> ServerName experimental RailsEnv production DocumentRoot /home/nowa/nowa_app/nowa/current/public <Directory /home/nowa/nowa_app/nowa/current/public > Allow from all Options -MultiViews </Directory> </VirtualHost> <VirtualHost *> ServerName api.experimental RackEnv production PassengerMinInstances 2 PassengerMaxPoolSize 10 DocumentRoot /home/nowa/nowa_app/services/api_gateway/current/app </VirtualHost> </code></pre> And working: <pre><code><VirtualHost *> ServerName experimental RailsEnv production DocumentRoot /home/nowa/nowa_app/nowa/current/public <Directory /home/nowa/nowa_app/nowa/current/public > Allow from all Options -MultiViews </Directory> </VirtualHost> <VirtualHost *> ServerName api.experimental RackEnv production PassengerMinInstances 2 PassengerMaxPoolSize 10 DocumentRoot /home/nowa/nowa_app/services/nowa_api_gateway/current/app </VirtualHost> </code></pre> Why is the output of apachectl -D DUMP_VHOSTS different? What have I missed? :C
Tags
<ruby-on-rails><apache><apache2><passenger><vhosts>
Title
Apache2 multiple name-based virtual hosts on one machine with rails/rack
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USdangerous.beans
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. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POApache2 multiple name-based virtual hosts on one machine with rails/rack
 UserUserId
 USgimboland
 VoteTypeVoteTypeId
 VTFavorite
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.