This message was deleted.

I am sure someone will give you a better answer, but what I do is search through github.com. It has a lot of great repos/commits with examples.

so, I would start with something simple like puppet-chrony first, then puppetlabs-apache (or puppet-nginx) and puppetlabs-postgresql/puppetlabs-mysql

See the

puppet-chrony

module at https://forge.puppet.com/puppet/chrony?src=slack&channel=puppet

generally everyone has their own wants on how they configure those services, so there are sane defaults in the puppet modules, but they leave it to the person making the app to choose

@David 'The Anvil' question for content and tooling team I’d say! It might be good idea to create some simple control repo with a few modules, unit tests and acceptance tests maybe

a good place to start is probably the control repo template https://github.com/puppetlabs/control-repo if you look at the forks you will find loads of real working control repos

I have this https://github.com/jay7x/puppetbolt-control_repo.. but 1) it’s designed for Puppet Bolt mainly (though trying to be as close to the usual control repo as possible) and 2) it’s not that simple and easy to understand I think

I also started with https://github.com/puppetlabs/control-repo

Wow thanks everyone for your responses. I am going to be checking these options and try them out.