Greetings, Les Mikesell!
>>> So how do you roll out code/configurations to a bunch of machines with
>>> the ability to roll back without storing it somewhere that the people
>>> who develop/test it can access?
>> You seem to be thinking that development engineers are allowed to touch
>> production. That is not how secure or even well run sites are operated.
> No, I'm thinking that development engineers develop the configurations
> that have to be tested and then deployed to production, and also the
> processes to do the deployment, because ummm, they're the ones that do
> development. And the operations people that manage the production
> servers need to be able to roll versions forward or backwards with fully
> tested configurations. So you either put complete configs under version
> control or you have operators making changes on the fly that can't be
Access credentials =/= project configuration.
You can maintain configuration in a project tree, although i wouldn't
recommend this, but access credentials is just too sensitive to be so careless
Two things that I can come up with, is
1. Access credentials has no impact on project, other than allowing or denying
it from operating. They can be either right or wrong, you do not really need
to track their changes.
2. It does not change often, in the meaning that you need some SERIOUS reason
to change source URI... i.e. actual deployment of a project, to connect it to
Andrey Repin (anrdaemon_at_freemail.ru) 02.10.2009, <22:46>
Sorry for my terrible english...
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-10-02 20:55:42 CEST