This project is read-only.

Orchard Eval

Topics: Customizing Orchard, General, Installing Orchard
Sep 1, 2011 at 7:39 PM

We’re evaluating Orchard CMS framework to develop client portals/widgets. Our goal is to develop once and reuse across many clients using different themes. We’ve developed few basic widgets as an eval and wondering… 

  • How can we deploy Orchard on top of SQL HA cluster (pub/sub model)?
  • How to promote code base and data to various environments (dev, test, stage/show, production) for Orchard modules, widgets, parts, type and themes?
  • How versioning works for various orchard pieces (module, widget, type, part)? 
  • Is it possible to develop module using custom metadata collection? 


Sep 1, 2011 at 7:43 PM

1. I'm sorry, I don't know

2. VCS may be used efficiently for code deployments. For data deployment, import/export is probably your best bet at this time, although a staging module would be a useful development.

3. We have a migration story, where modules can describe to the system how to upgrade from one version to the next.

4. What is a custom metadata collection?