Add instructions to create a new module

[ekohl]

No description provided.

[bastelfreak]

be use? Is that a correct phrase?

[bschonec]

As someone who's never used modulesync_config before, the line, "First add it to 'managed_modules.yml'" isn't clear. The yml file has pre-loaded modules such as 'puppet-conntrackd'. If I'm trying to create a new module (from scratch?) then is it necessary to remove all of the pre-loaded entries in manage_modules.yml? Since my module is not in the Puppet forge, what is the correct format to enter? Is it the path to 'git clone' the module?

[kenyon]

I think it's supposed to be

Suggested change

	If it's not in the voxpupuli namespace, be use to include yours.
	If it's not in the voxpupuli namespace, be sure to include yours.

But it could be clearer, like @bschonec said.

What I did was create a branch in my fork that changes the namespace setting, but not sure how maintainable that is: master...kenyon:modulesync_config:kenyon

[ekohl]

You can add kenyon/puppet-powerwall_dashboard instead, removing the need to override the namespace in the config.

While writing this I also considered changing modulesync to remove the global setting and simply use full qualified names everywhere.

[ekohl]

The yml file has pre-loaded modules such as 'puppet-conntrackd'. If I'm trying to create a new module (from scratch?) then is it necessary to remove all of the pre-loaded entries in manage_modules.yml?

No, I used "add" so that implies you don't need to remove other entries.

Since my module is not in the Puppet forge, what is the correct format to enter? Is it the path to 'git clone' the module?

I've added an example format.

[bastelfreak]

lol, nice hack 'abusing' basename!