Special:Badtitle/NS1198:Best practices for development of EZ templates/2/en

• Make sure your EZ template does not share RPMs with other EZ templates. For example, if you submit a mysql application template, make sure that the mysql package is used only by it and not any other application template, e.g., wordpress.
• Minimize the number of RPMs in packages files. For example, do not list every RPM implied by dependencies.
• Use setname when you modify an OS EZ template. This will help you avoid code duplication.
• Make sure all your scripts have error-handling routines and return 0.
• Add comments explaining the reasoning behind the code in scripts that is not intuitively clear.
• Make your EZ templates as universal as possible. Avoid specific modifications like localization, time zones, etc.
• Avoid using complex routines in your scripts to make them easier to maintain.