Skip to content

Commit 7037681

Browse files
Suzie Baunsgardnpwalker
authored andcommitted
Edits to Slack, Before Starting, What you get
* Edits to Slack, Before Starting, What you get * Fix slack channel language and config_version
1 parent a5fe635 commit 7037681

File tree

1 file changed

+6
-10
lines changed

1 file changed

+6
-10
lines changed

README.md

Lines changed: 6 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -21,27 +21,23 @@ Table of contents
2121

2222
# Join the #ramp-up channel on Puppet Community Slack
2323

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.
2725

2826
# Before starting
2927

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.
3329

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.
3531

3632
# What you get from this control-repo
3733

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 best practices installation of PE including:
3935

4036
- A Git server
4137
- 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`
4339
- 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
4541

4642
# How to set it all up
4743

0 commit comments

Comments
 (0)