The SIMP project came up with the idea of 'component profiles'. These are
profiles that are meant to be shared but that work best within a specific
ecosystem.
Though our naming is a little askew at the moment, we currently use
'simp_' as the component profile and '' as the component
module.
For
Hrm, I wonder how much this has to do with definitions of what a profile
module is. To me, a profile module includes a lot of component modules and
conditional logic and an occasional primitive (include apache, include a
logrotate config, conditionally manage all cron jobs or not). What you're
Thanks Martin, the PSIC repos are excellent - thanks!
And Tim, the logic of having the p_ modules avoiding namespace collisions
also makes perfect sense at scale.
I was thinking more of a searchable, more goal oriented view of sharing
Profiles that implement 1 or more technologies to form a
