Custom modules/themes in Azure (idea proposal)

Jan 16, 2011 at 12:48 PM

I think it would be awesome if we could upload Moduels/Themes to Azure hosted Orchards. I understand that the implementation of today does not support this but here's a proposal on how it could be acheived.

  1. All modules/themes/packages is uploaded to the blobstorage.
  2. When an instance starts and during certain intervals/cycles this storage is checked for new module (or using the queue or some kind of trigger)
  3. Packages are then installed

Same should go for activation of features, each node should check the central repository if the feature should be activated on the node.

Migration and other activation features should only run on one node.

Just a few minutes of thinking, but allowing this would make it far less painful than the current way of doing it.

Or, do you have any other plans for this.



Jan 16, 2011 at 4:59 PM

That's a good idea for vNext. File a bug in the issue tracker with this explanation, you will be able to follow the dev, and comment the design.