Press Ctrl / CMD + C to copy this to your clipboard.
This post will be reported to the moderators as potential spam to be looked at
We set up an Umbraco website which is now Live using Umbraco 7.1.6.
We are going to start having multiple developers work on the website building controls, models, etc.
So what I did was set up a Visual Studio project using NuGet, Umbraco and the current files from our website.I tossed it up on Beanstalk Subversion. Now... What is the best practice for developing using Umbraco. Since the nodes, media, package info, and doctypes are tied to the DB, what would be the best approach.
Our plan is to have a local dev (per developer tied to SVN), a Test Website and a Live (Production) website.
What is the best approach for the DB?Should every developer have their own copy of the Live DB?Should all local dev site point to the Test Website DB?How should we port Doctypes, Media and Content nodes to from local Dev, to Test to Production? (Courier is an option we are exploring).
But we want to eventually have all DB's in sync. What would be the best approach to have all DB's in sync as well as all the dev/Test/Live website.
Thoughts? I would be interested to hear how the Umbraco crew does their development.
We are currently using a shared DB for all local developers and separate ones for stage and production. We use USync to keep the development objects in sync but we have not found it critical that content remain synchronized.
We are still in active development (our site has 6 major parts, 4 of which are live) so this may change as we move more towards maintenance but here's what we're doing now.
Environment: Visual Studio project using NuGet. Source control with Team Foundation Server.
is working on a reply...
Write your reply to:
Image will be uploaded when post is submitted