jstruebel
commented
8 years ago After I converted most of the tklpatches that I had created I've started thinking about how this would be best implemented. I came across the debops project which looks interesting, possibly have tkl specific play books that leverage their roles. I'm not sure if that might be an issue down the road if they go in a different direction from Turnkey Linux.
I do think that the best way to structure the repository is to have one role per service,e.g. ssh, postfix, MySQL, etc. Similar to the debops project, each role would leverage variables to define the specifics of the configuration. I started with the approach of just converting my patches into roles, but it is fragile for some services, e.g. Samba, vs using variables and templates which seems to be the method that fits best with the design of ansible.
Thoughts?
JedMeister
@jstruebel suggested that now we have an Ansible appliance (thanks @Dude4Linux for that! :smile: ) that we should consider using a repo of Ansible scripts (developed by the TurnKey community) as a way to easily share tweaks and customisations.
Currently the easiest way is to use TKLPatch, but as Jonathan rightly points out; it's targeted for use on ISOs rather than installed systems. If you wish to use a container you need to tweak the ISO then build the container image. Using Ansible scripts would be a much neater way to go.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.