Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m a web developer, we have a production site that is the latest & greatest of our site (lots of Coldfusion). Would it be wise to put our production site under version control as a git server?
Drawbacks? Benefits?
More or less, I’m envisioning that I will put git on the production side of things as the orgin branch/master then once we are ready to go live push to our production. Is that wise?
You can’t push to a non-bare repository, because your push might overwrite changes in the working directory that your local repo can’t know about.
Most people using git for deployment like you’re talking about have their production directory as a git repository, and they pull TO it, from INSIDE it to get updates. Either from a central repo somewhere, or an integration manager’s local repo, or something like that.