Fix README
This commit is contained in:
parent
8891ae825a
commit
40be8a0205
|
@ -13,13 +13,11 @@ There are two ways to create the boilerplate for the puppet module.
|
|||
### Locally
|
||||
|
||||
1. Clone locally the [cookiecutter-openstack-puppet-modules](https://github.com/enovance/cookiecutter-openstack-puppet-modules.git) repository.
|
||||
2. Edit the `cookiecutter.json` file to specify the name of the new project
|
||||
3. Run `cookiecutter /path/to/cloned/repo`
|
||||
|
||||
### Remotely (ie. using a git repo)
|
||||
|
||||
1. Fork the [cookiecutter-openstack-puppet-modules](https://github.com/enovance/cookiecutter-openstack-puppet-modules.git) repo
|
||||
2. Edit the `cookiecutter.json` file, commit and push
|
||||
3. Run `cookiecutter https://url.to.your.fork/`
|
||||
|
||||
## What's next
|
||||
|
@ -27,4 +25,5 @@ There are two ways to create the boilerplate for the puppet module.
|
|||
Once the boilerplate created,in order to be compliant with the other modules, the files managed by msync[1][2] needs to be in the project folder. Once synced module is ready, announce its existence to the ML, make the proper patch to openstack-infra and finally wait for the reviews to do the rest.
|
||||
|
||||
[1] https://github.com/puppet-community/modulesync
|
||||
|
||||
[2] https://github.com/stackforge/puppet-modulesync-configs
|
||||
|
|
Loading…
Reference in New Issue