In this Tinderbox meetup, we discussed strategies for creating Tinderbox best practices, and shared a few, e.g., 1) working with |=, 2) organizing containers, 3) use of root, 4) use of separators, 5) logging, 6) “be kind to your future self”, and others.
References
Proxmox, Simplify your data center, Secure, flexible, and reliable open-source enterprise solutions. For the highest demands and tight budgets in professional IT environments.
Following up, we hope to encourage some community participation and make this “Best Practices” Tinderbox a living document.
I think it’s intended for all Tinderbox users, though the content may range the gamut from beginners to experienced pros.
The idea is to leverage the experience of long-term, or more advanced users, to aid any user in achieving their goals in using Tinderbox more quickly, or with less friction, by avoiding pitfalls, or exploiting powerful features that may be elusive to the less experienced user.
I think we want to move this discussion to its own topic. There was mention during the meetup that we may wish to thread each “best practice,” so the discussions remain more focused. I’ll leave that to the admin(s), as I have no experience in running a forum of this kind.
For the indeterminate future, we plan to devote the first ten minutes or so of each Tinderbox meetup to a discussion of the Best Practices document, answering questions, adding new ideas or reviewing old ones.
So by all means, download the file attached above and take a look at it. At some point soon, I think it’ll be renamed and added to the new topic or category and be updated regularly.