This project is read-only.

Deploying Orchard from source drop after adding content locally

Topics: Administration, Customizing Orchard
Jun 18, 2013 at 1:32 AM
I'm trying to deploy an Orchard site after setting it up a little bit locally. Is this not the way it's designed to work, because modules seem to randomly break when I copy my files into my staging directory. Should content only be created on the production site? My steps are roughly:
  1. enlist source and baked new default recipe
  2. added some blog articles, navigation, tags, etc (basic content)
  3. added several installed modules (and Mango theme) to Orchard.sln for debugging purposes
  4. modified some source on the LatestTwitter module
  5. build "compile;package" (no errors/warnings)
  6. copy build/stage to staging IIS
  7. copy contents of App_Data folder to staging IIS (since it's not output from build command)
At this point, the site loads, but several modules don't even show installed on the gallery page: Vandelay suite, LatestTwitter, FollowMe even though some of them seem to sort of work and others don't.

What's a basic strategy for managing a website from a source drop after modifying it locally? Or is there some way to always overwrite my local data with what's in production if I want to test some changes?
Jun 26, 2013 at 7:12 AM
Also edit Orchard.proj to include the modules you need into the deployment package.