Hi, I've been doing some customizations on my eBox 1.4 install to setup the webmail on SSL with certificate authentication and more ideas to come next.
Currently what I'm doing is modifying directly the mason templates under /usr/share/ebox/stubs/ after making a backup of each, even if I now this is not a good practice as any update on the ebox modules affected could overwrite them as stated in the documentation at:
http://doc.ebox-platform.com/en/develop.html#service-advanced-customizationAnyway, what could be a better approach using hooks? Should I backup and overwrite the files in /usr/share/ebox/stubs with my custom version at each module start in the preservice and postservice scripts or is there a better way?
Thanks for any suggestion.
Marcello
Topic: best practices for hooks, stubs and templates (Read 1457 times)