This content has been marked as final. Show 5 replies
user964802 wrote:In my opinion , it is better to have Production Environment always an Execution Repository
Is it always a good idea to make the Production Environment an Execution Repository.
In this case , only scenario (compiled code) can be imported from a dev environment , thus reducing the scope of unwanted changes .
Is there a good case for making it a Development Repository?I am not aware of any .. please do share if you find a good case.
I agree with Sutirtha, it's a very good practice to set as an execution repository. It ensures that nobody changes implementation in production and forces you to fix issues in Dev environment.
I have one question. W have to physical database servers one for dev - test and one for production. Where to put Master repository, which database dev, test or production?
You can put it on dev-test or on production, it doesn't change much.
I think I would go for prod so you're sure that everything runs well even if dev-test DB is down.
Thank you for your respond.