This project is read-only.

General guidance for custom development

Topics: Administration, Customizing Orchard, Writing modules
Mar 7, 2013 at 8:53 PM
I'm currently in the process of evaluating Orchard as the core platform for a new website. A number of custom modules will need to be written in order to fill the site requirements. I have read a number of posts recommending a full checkout & build of the source code rather than simply running the installer and building/installing custom modules.

1) Is this really the best practice, and if so why?
2) Assuming this is the recommended approach, what precautions can be taken to ensure future Orchard upgrades play nicely with the customized site?
Mar 7, 2013 at 8:58 PM
  1. yes. Source control is good. Not sure what to add to this. If you ever need to debug the application, and you will, it's best to have the full source code.
  2. Never modify the core or modules that are not yours, unless your intention is to fix a bug and contribute patches or new features. Otherwise, it's really easy, you'll just merge the changes in.
Mar 7, 2013 at 9:16 PM
Thanks - your response along with the information in this post regarding the Orchard repository existing alongside local module repositories was very helpful.