Tom Mollerus' Weblog

• Provide a configuration file which contains all of the necessary settings that users would need to change to personalize or install the application.
• Try to organize your files well, using separate folders for separate functions (e.g., application code, templates, uploaded content, etc.). Try to keep the files that users would modify or contribute in very specific folders.
• Joshua explained that he encrypts certain files not so much to protect source code or intellectual properties, but to control where users make their customizations.
• Then when it comes time to make an upgrade available, you can overwrite the contents of certain folders and leave the user-modified folders alone.
• Finally, Joshua discussed the great technique of using a well-designed, browser-based form for your installs versus the usual technique of having the developer read an install file and then make manual text changes to the config file or Application.cfc (I've used the former, but am still guilty of the latter in most projects).

After the preso, a bunch of us headed across the street to The Grand Canal, where, as is my habit with speakers, we treated Joshua to drinks. Thanks again, Joshua!