You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+6-10Lines changed: 6 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,27 +21,23 @@ Table of contents
21
21
22
22
# Join the #ramp-up channel on Puppet Community Slack
23
23
24
-
Our [Puppet Community Slack](http://slack.puppet.com) is a great way to interact with other Puppet users. The #ramp-up channel is specifically for users talking about starting with PE and using this repository.
25
-
26
-
Other channels in the Puppet Community Slack are great for asking general Puppet questions as well.
24
+
Our [Puppet Community Slack](http://slack.puppet.com) is a great way to interact with other Puppet users. The #ramp-up channel is specifically for users who are new to Puppet Enterprise and using this repository. Other channels in the Puppet Community Slack are great for asking general Puppet questions.
27
25
28
26
# Before starting
29
27
30
-
This control-repo and the steps below are intended to be used during a new installation of PE.
31
-
32
-
The instructions are geared towards a new installation of PE2015.3.z. However, the control-repo should work just fine on [PE2015.2.z](#upgrading-to-pe20153z-from-pe-20152z)
28
+
This control-repo and the steps below are intended to be used with a new installation of PE 2015.3.z. However, you can use existing installations of 2015.3.z, including [upgrades from 2015.2.z to 2015.3.z](#upgrading-to-pe20153z-from-pe-20152z), if you complete some additional steps.
33
29
34
-
If you intend to use this control-repo on an existing installation then be warned that if you've already written or downloaded modules when you start using r10k it will remove all of the existing modules and replace them with what you define in your Puppetfile. Please copy or move your existing modules to another directory to ensure you do not lose any work you've already started.
30
+
**Warning:** When using an existing PE installation, running `r10k deploy environment -pv` removes all existing modules and replaces them with with the modules defined in your [Puppetfile](https://docs.puppetlabs.com/pe/2015.3/cmgmt_puppetfile.html). Please copy or move your existing modules to another directory to ensure you do not lose any work.
35
31
36
32
# What you get from this control-repo
37
33
38
-
As a result of following the instructions below you will receive the beginning of a best-practices installation of PE including...
34
+
When you finish the instructions below, you will have the beginning of a bestpractices installation of PE including:
39
35
40
36
- A Git server
41
37
- The ability to push code to your Git server and have it automatically deployed to your PE master
42
-
- A config_version script to output the commit of code that your agent just applied
38
+
- A config_version script that outputs the most recent sha for your code deployment each time you run `puppet agent -t`
43
39
- Optimal tuning of PE settings for this configuration
44
-
- Working and example roles/profiles code
40
+
- Working and example [roles and profiles](https://docs.puppetlabs.com/pe/2015.3/puppet_assign_configurations.html#assigning-configuration-data-with-role-and-profile-modules) code
0 commit comments