Contents tagged with deployment
-
Orchard Brotips: modules you should keep enabled/disabled in production or during development
Although with the Precompiled build target, coming with Orchard 1.6, modules can be precompiled into dlls, it's still good practice to disable every feature you don't need in production even if the performance penalty is small. Here's a small list of common modules you should watch out for.
-
Orchard Brotips: deploy without .hg folders
The Orchard web project file, Orchard.Web.csproj contains a line that tells the compiler to include (among others) modules and themes in the result package too. That one currently has a slight, but important glitch: the pattern for excluding Mercurial-related files is broken. Therefore, if you have subrepositories in you solution (like it's frequent with modules or themes) their .hg folders will also be in the deploy package. With big repositories, besides deploying a bunch of unnecessary files, this can even cause errors when publishing: