I managed to setup dnn, but only for local dev.

now want to setup for team environment.

say I setup the dnn on devSvr1, we got 4 developers, each developer will dev the web/main site locally.

can/should I setup the dnn locally on their machine, then later just change the db connection point to using central (1) dev db?

what I want to achieve is the the dnn changes/update of contents is centralized/global to each local development main site

 

Are you developing custom modules or what? I have found it best to have each developer work against a local copy of DNN (both code base and database) and then have a central dev site set up where they changes get pushed to for testing. Not having the content be synched up on all developers machines has not been an issue.

But, that is just the way we do it. YMMV. :)

Robert

this is what I intended:

we want to test stuffs locally, on developer own machine.
But I want the dnn to be kind of centralized, especially the content. so someone test/update/deploy something onto the dnn, it will reflect to the rest of the developers local test environment.

plan to do:
1 dev server hosting dnn, and db

all developers will copy the dev dnn web folder onto local, and setup the web folder locally, since the web.config setting is the dev server, it can/should mimic as the central dnn, right?

I want/need this local dnn, as our local web app can setup a virtual dir to this local dnn (sub)portal site, using URL Rewrite in our main app as routing. Can't do this easily using local main app but attempt to point to the central dnn site.