workflow - Mercurial & Web Development: How to handle publishing/deployment? -
We are not going to any SCM from Mercurial at work. This is a bit of a learning curve, but after two days of messing with it I definitely feel more comfortable with it.
There is still a big, unconfirmed question in my mind: Once the code is over, how do we handle the actual deployment?
Should we run a copy of Mercurial on production (live) server? Or should we set up RCIN or something to synchronize the web directory with the riyas? What is the best practice here?
If we point to Apache as Apache, then I think it's okay unless we focus on Or is it just a terrible idea of Repo to say Apache and should I do something else? Regarding the topic, I have heard a few things about inserting any upgrade scripts (such as schema changes for MySQL) under version control, so they can be participated when the version is deployed. But how will it work as part of the workflow? I would not like to keep it / everything, because it is a temporary one-time script ... Thanks for any advice you guys can give. I recently searched for I still appreciate any feedback that you guys know whether it is a good idea or not. hg update a separate, non-static branch? Although it still seems a little dangerous for me. Is there any way to force it to create it in some way?
hg archive command, so I It seems that instead of w / I have written a Bash script, changing it to the head of 'Production' branch, then archives it for the predefined destination. Seems to work.
Comments
Post a Comment