Skip to content
Snippets Groups Projects
Commit f0006b62 authored by Nicolas Dandrimont's avatar Nicolas Dandrimont
Browse files

Update wording in README.md following site/profile/role merge

parent f96f8c7f
No related branches found
No related tags found
No related merge requests found
...@@ -36,14 +36,12 @@ demonstrated by the following series of articles: ...@@ -36,14 +36,12 @@ demonstrated by the following series of articles:
- http://garylarizza.com/blog/2014/03/07/puppet-workflow-part-3b/ - http://garylarizza.com/blog/2014/03/07/puppet-workflow-part-3b/
- http://garylarizza.com/blog/2014/10/24/puppet-workflows-4-using-hiera-in-anger/ - http://garylarizza.com/blog/2014/10/24/puppet-workflows-4-using-hiera-in-anger/
Our main manifests are present in the `swh-site` repository. Each branch Our main manifests are present in the `swh-site` repository. Each branch of that
of that repository corresponds to an environment. The default repository corresponds to an environment in the puppet workflow presented.
environment is `production`. This repository contains the Puppetfile
referencing all the modules, the main manifest file `manifests/site.pp`, This repository contains the Puppetfile referencing all the modules, the main
and the hiera `data` directory. manifest file `manifests/site.pp`, and the hiera `data` directory, as well as
the two "site-modules" for `profile`s and `role`s.
Roles of Software Heritage servers are defined in the `swh-role` module.
Profiles are defined in the `swh-profile` module.
Our setup mirrors the git repositories of third-party Puppet modules on the Our setup mirrors the git repositories of third-party Puppet modules on the
Software Heritage git server --- this is to avoid reliance on 3rd party Software Heritage git server --- this is to avoid reliance on 3rd party
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment