App_Data - file explanation (managing environments / automated deployment)

Topics: General
Mar 22, 2011 at 12:29 PM

I'm trying to get my head around how we manage environments/deployments with regards to Orchard, and trying to understand a little more about the files in App_Data - specifically what the following do :

 

mappings.bin

cache.dat

reports.dat

_marker.txt

hrestart.txt

Settings.txt (specifically what are the hashes used for ? - I get that it controls where the cms's db lives)

 

Currently, I'm guessing my deployment process will look like :

(When moving from local to staging - note I'm using appharbor, so you push the entire codebase, and appharbor builds and deploys the code)

1) Rewrite Settings.txt to point to staging

2) Sync the databases (ie push changes from local to staging)

But I'm not sure about the other files in App_Data - can these be ignored, or do they need to go too ? For example, I noticed that when I enabled a custom module, mappings.bin was also altered - would I need to push this to staging too ?

 

Is anyone else trying to do automated deployment in a similar manner ?

 

Thanks for any advice and help,

Ben

Coordinator
Apr 1, 2011 at 12:22 AM

I posted an explanation of what's in app_data here: http://orchardproject.net/docs/Developer-FAQ.ashx?NoRedirect=1#Whats_in_App_Data_15