Anyone using a pre-commit hook in subversion to test for syntax errors in templates? I wondering if it might help a client prevent checking in a broken site-wide template.
I'm releasing an application to a client. They are a small organization with limited technical expertise. In the past they all shared a single unix account and used ftp (some plain text!) to maintain their site's content. (The result of this ftp usage is a collection of files with different line endings and different encodings.) It's going to be challenge to move them to reversion control and the use of a staging server. The new application has a mini-cms for managing the bulk of their content, but there's still quite a bit that needs to be managed on the file system, such as non-text files and templates used system wide (e.g. for site layout). I'm not sure if there's an easier (less complex) way to go, but I'm going to setup subversion for them so at least they have version control and the security of ssl. Since they will be able to edit site-wide templates I thought it would be good to use a pre-commit hook script to at least check for syntax of templates before they are committed. I'm not sure they will always Anyone doing something like this? And more off-topic: Any better suggestions that subversion for a client like this? I think the commercial offerings (like Perfoce) might be more than they are prepared to use (or administer). Any suggestions for Windows and Mac GUI-subversion clients? -- Bill Moseley [EMAIL PROTECTED] _______________________________________________ templates mailing list [email protected] http://lists.template-toolkit.org/mailman/listinfo/templates
