Tracking Back Office Changes - Moving the Media file around
Hello Guys,
Currently when I develop an Umbraco project using GitHub i run into the following issues:
- If you make changes to the back office (new doc types for example) on a development DB. Then swap over to say UAT how do you track those changes and replicate them onto UAT DB?
- What do you do with the damn media file :) ? This thing can get HUGE and its not a good idea to ever commit/ push this to GitHub. How do you guys deal with this file throughout the project? Do you just copy it out to a storage area and copy it back in when you update your repo?
Tracking Back Office Changes - Moving the Media file around
Hello Guys,
Currently when I develop an Umbraco project using GitHub i run into the following issues:
- If you make changes to the back office (new doc types for example) on a development DB. Then swap over to say UAT how do you track those changes and replicate them onto UAT DB?
- What do you do with the damn media file :) ? This thing can get HUGE and its not a good idea to ever commit/ push this to GitHub. How do you guys deal with this file throughout the project? Do you just copy it out to a storage area and copy it back in when you update your repo?
Cheers,
James.
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.