On Oct 5, 2007, at 8:51 PM, Wade Preston Shearer wrote:
I am interested in opinions on where best to locate a repository.
Concider the following situation:
There are individual development environments for each developer. They
commit their code to the repository. Code is updated on a common "dev"
server from the repository for testing. When updates or releases are
ready to by published, the code involved is then updated on a beta
("staging") server (that identically matches the production servers)
from the repository where it is confirmed to be ready. Once verified,
the code is then updated on all production servers (behind a load
balancer) from the repository.
Myn question is where would you put the repository? All servers have
to have access to it. I like the idea of putting it on the dev server,
but for security, the production servers can currently only
communicate with beta. So, with my current setup, the repository would
have to be on beta.
If you were setting up a system such as this, how would you do it?
If the production servers can only talk to the staging server then
you need to have at least a mirror of the repository on the staging
server. And that is probably how I would do it. The master
repository (the one that developers commit and sync to) can be some
where else, like the dev server. Or for that matter any other box.
--
Joseph Scott
http://joseph.randomnetworks.com/
_______________________________________________
UPHPU mailing list
[email protected]
http://uphpu.org/mailman/listinfo/uphpu
IRC: #uphpu on irc.freenode.net
