StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
10647080
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
7
CommunityOwnedDate
CreationDate
2012-05-18T05:18:29.383
FavoriteCount
0
LastActivityDate
2017-06-08T14:32:28.477
LastEditDate
2017-06-08T14:32:28.477
LastEditorUserId
1783163
OwnerUserId
1206051
ParentId
10631933
PostTypeId
2
Score
793
ViewCount
0
LastEditorDisplayName
text
Body
I have found answers to my confusions. There is a very important difference between the <code>root</code> and the <code>alias</code> directives. This difference exists in the way the path specified in the <code>root</code> or the <code>alias</code> is processed. In case of the <code>root</code> directive, full path is appended to the root including the location part, whereas in case of the <code>alias</code> directive, only the portion of the path NOT including the location part is appended to the alias. To illustrate: Let's say we have the config <pre><code> location /static/ { root /var/www/app/static/; autoindex off; } </code></pre> In this case the final path that Nginx will derive will be <pre><code>/var/www/app/static/static </code></pre> This is going to return <code>404</code> since there is no <code>static/</code> within <code>static/</code> This is because the location part is appended to the path specified in the <code>root</code>. Hence, with <code>root</code>, the correct way is <pre><code> location /static/ { root /var/www/app/; autoindex off; } </code></pre> On the other hand, with <code>alias</code>, the location part gets dropped. So for the config <pre><code> location /static/ { alias /var/www/app/static/; autoindex off; } </code></pre> the final path will correctly be formed as <pre><code>/var/www/app/static </code></pre> See the documentation here: <a href="http://wiki.nginx.org/HttpCoreModule#alias" rel="noreferrer">http://wiki.nginx.org/HttpCoreModule#alias</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PONginx -- static file serving confusion with root & alias
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USpeterh
UserOwnerUserId
1. UStreecoder
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PONginx -- static file serving confusion with root & alias
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
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.