Closed singuerinc closed 7 years ago
I'm wondering what's the correct way of change the site.pp file without breaking Boxen any time I merge it with the upstream.
I can see your point with wanting to strip these out and if you want to provide a pull request I'd be happy to review it. I would probably wrap this in a couple of if
's and then set a sensible default in the user manifest to install by default but allow people to opt out if needed. Here is how I would approach it
# site.pp
if $::install_nodejs {
nodejs::version { '0.8': }
nodejs::version { '0.10': }
nodejs::version { '0.12': }
}
Where $::install_nodejs
is managed by a YAML compatible Puppet manifest.
I also want to remove dnsmasq and nginx but as they seems to be "core" modules maybe is not a good idea to remove them.
If you have any applications being managed/served locally using Boxen, I'd recommend leaving them. I would vote a strong :-1: on removing these as I see them as a pretty core part of the local development setup for a large portion of the user base.
Because I develop all in Docker machines I don't want to install a bunch of node+ruby versions on my system.
I'm wondering what's the correct way of change the
site.pp
file without breaking Boxen any time I merge it with the upstream.Basically I want to remove these lines:
I also want to remove
dnsmasq
andnginx
but as they seems to be "core" modules maybe is not a good idea to remove them.