StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20596355
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-12-15T15:48:02.387
FavoriteCount
0
LastActivityDate
2013-12-15T15:48:02.387
LastEditDate
LastEditorUserId
0
OwnerUserId
244037
ParentId
16367220
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
So it seems there's some disconnect on the understanding of how this is meant to work. When writing a recipe, it's common to use node attributes to define where thing will end up - such as your web_root directory. I can conceive of the recipe's attributes file containing: <pre><code>default['base_directory'] = '/var/www/html' </code></pre> Which would apply to many production servers out there. Then, when writing your recipes, use this attribute to send the files where you want them to, e.g.: <pre><code>cookbook_file "#{node['base_directory']/css/myfile.css" do owner "root" ... end </code></pre> When sharing your cookbook, anyone executing this on a server that has the <code>/var/www/html</code> directory will receive your file in the correct place. In your Vagrantfile, in order to override the node's <code>base_directory</code> attribute to the synced directory, you can do something like this: <pre><code>SYNCED_FOLDER = "/synced/dir/on/vm" Vagrant.configure("2") do |config| config.vm.synced_folder ".", SYNCED_FOLDER config.vm.provision :chef_solo do |chef| chef.json = { "base_directory" => SYNCED_FOLDER } end end </code></pre> However, you mentioned that you didn't want to have to specify <code>base_directory</code> in your recipes, so I'd ask what node attribute you are using to drive the target location of your web root? If you're using something like the apache2 cookbook from the Community site, then there's <a href="https://github.com/opscode-cookbooks/apache2/blob/master/attributes/default.rb#L33" rel="nofollow">already an attribute</a> for this: <code>node['apache']['docroot_dir']</code>, so using that you can control where thing are referenced.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POProgrammatically get Vagrant property in Chef solo recipe
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USMike Fiedler
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POProgrammatically get Vagrant property in Chef solo recipe
 singulars
 PostTypePostTypeId
 PTQuestion
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.