I've been tasked with trying to setup a proper deployment plan for our current DNN installation. We have DNN Plattform 7 with a single Site, and I've hit several road blocks I'm hoping you could help with.

I'm currently at loss on whether I should keep the entire DNN installation in git, or if I should break it up into multiple repositories.

I'm also unsure what folders/files I can tell git to ignore.
DNN and modules alike seem to be writing cache files, temp files, and other unknown files several places, like APP_DATA and within Portals (not the Cache folder mind you).

I tried googling to find some kind of description of DNN's folder structure, but no dice.

So if anyone has a decent git config to share, or advice on how you track and deploy your DNN instance(s) I would be forever grateful.

Thank you.

We still need a way to track custom files to have a local version as close as possible to the one in production.

Currently I have a script which creates and restores the production database to a local instance, a very important tool when debugging errors in production.

Ideally we should be able to version control all files that we change manually, without tracking files generated by DNN or modules.

web.config, robots.txt are examples of files we want to version control at root level. (All credentials are pull out into untracked files of course)
And inside Portals we probably want to version control most of the site files like Skins, templates and containers. Maybe just ignore some of the obvious folders like Cache, EventQueue and Logs.

I was just hoping someone had good suggestions on how to handle this and deploys.

If what you're running locally and what you're running is production is diverging too much, it's hopeless to debug something locally anymore.

Thank you very much, this was exactly what I was looking for!