StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20659279
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-12-18T13:16:42.513
FavoriteCount
0
LastActivityDate
2013-12-18T21:06:43.060
LastEditDate
2013-12-18T21:06:43.060
LastEditorUserId
550618
OwnerUserId
550618
ParentId
20591316
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
<code>Directory</code> is a directive targeting a file system directory, and should always have a path (waildcards allowed). Using some instructions targetd to no directory may be discarded silently, or maybe with an error (you could test it), but is would certainly be useless. Why would you write some configuration instructions targeted to no directory at all? But there's maybe more things in your question. Ususally a Virtualhost should contains at least one Directory instruction, the DocumentRoot directory, and usually we also add one targeting the root of the filesystem, this way: <pre><code><Directory /> (instructions to deny access and avoid .htaccess reads) </Directory> <Directory /my/document/root/> (instructions to allow access and still avoid .htaccess reads or to allow them if you are lazy and feel over confident that .htaccess are useful in any way and you do not need speed) </Directory> </code></pre> And you could add more, especially to avoid usage of <code>.htaccess</code> files as such file stored in <code>/path/to/somewhere</code> is the same thing as a <code><Directory /path/to/somewhere></code> section, but slower. Now you do not like to repeat yourself in your VH configuration, so you coud maybe use .htaccess files or global level instructions for things that are usually set there. And you could also use another magical keyword, which is Location. You can use a lot of Apache instruction in a <code><Location /foo></code> directive. Locations works on url, not on filesystem paths. So <code><Location /></code> is your documentRoot, and <code><Location /foo></code> is maybe the subdirectory 'foo' under you DocumentRoot. This could help you write things in your VH without reusing the documentroot prefix everywhere. But be careful, urls are not file-system paths. Any protection applied on the url level may be weaker or stronger compared to a protection applied on a directory level. It depends on your alias, the way you use urls, etc. Update: If you use the new Apache 2.4 version you can now use <a href="http://httpd.apache.org/docs/current/mod/mod_macro.html" rel="nofollow">mod_macro</a> or even easier, <a href="http://httpd.apache.org/docs/current/en/mod/core.html#define" rel="nofollow">built-in variables support</a>: <pre><code>Define docroot "/path/to/mysite" DocumentRoot ${docroot} <Directory ${docroot}> (...) </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POApache: <Directory> directive with no path specified
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USregilero
UserOwnerUserId
1. USregilero
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POApache: <Directory> directive with no path specified
 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
 VTAcceptedByOriginator
2. 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.