Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixing #1088 - Adding puppet file configuration to copy index.html file ... #1115

Closed
wants to merge 2 commits into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
18 changes: 14 additions & 4 deletions v1/docs/getting-started/provisioning.md
Expand Up @@ -86,6 +86,15 @@ class apache {
}

include apache

file { "/var/www/index.html":
ensure => present,
source => "/vagrant/index.html",
owner => "root",
group => "root",
require => Class['apache'],
}

{% endhighlight %}

We then add support in the Vagrantfile to support Puppet provisioning:
Expand All @@ -102,10 +111,11 @@ end
Alternatively you can run Puppet in client-server mode by enabling the `:puppet_server` provisioner. See the [Puppet Server](/v1/docs/provisioners/puppet_server.html) documentation for more details.

**Note:** The Puppet example above is not quite equivalent to the Chef example,
Apache isn't properly configured to serve our `/vagrant` directory. The main
purpose here is to show you how Puppet provisioning works with Vagrant. You
can imagine how you would configure Apache further to serve from the `/vagrant`
directory.
Apache isn't properly configured to serve our `/vagrant` directory; instead we
have configured puppet to copy the `index.html` file to the default webroot
directory. The main purpose here is to show you how Puppet provisioning works
with Vagrant. You can imagine how you would configure Apache further to serve
from the `/vagrant` directory.

## Running it!

Expand Down