This project is read-only.

orchard module deployment strategy

Topics: Administration, Installing Orchard
Jul 20, 2015 at 10:04 AM
At the moment, we are using orchard gallery to deploy some modules we internally develop.

We have several environment (dev, qa, staging live), and we setup dev, qa, staging and live orchard gallery to upload our modules.

Now everyone feels it is a pain to maintain so many galleries, as we have to build the modules, then manually upload to the gallery and then go back to orchard cms admin to get the updates.

It will be nice if we build the module in a build tool and then just deploy to orchard cms's admin site. (maybe we can run some api call to enable the updates)?

Is it possible? If is, will there any issues?
Jul 20, 2015 at 5:39 PM
All you need to do is copy the modules to you Orchard's installation. No need at all to go through the gallery.
Jul 20, 2015 at 5:48 PM
Do you mean everything (including project file, c# code etc)? Then Orchard will find this change and compile on the fly?

Is there some documentation I can have a read?
Jul 21, 2015 at 8:46 AM
A module is just a separate project, so you can use the Publish feature of Visual Studio. Right click on your module, click publish and enter the settings. You can also, just as sfmskywalker mentioned, just copy the source over to the modules folder of your web application.