Deployment (moved): Difference between revisions

← Older edit

Deployment (moved) (view source)

Revision as of 19:16, 18 February 2014

956 bytes removed , 10 years ago

updating link

Anonymous user

imported>Brittag

Revision as of 20:07, 27 September 2011 (view source) imported>Paulproteus (Created page with '{{Hacking OpenHatch}} This is a quick-and-dirty page explaining how to deploy new versions of the OpenHatch code. == Prerequisites == * You must be part of the Login team …')		Latest revision as of 19:16, 18 February 2014 (view source) imported>Brittag (updating link)
(8 intermediate revisions by 2 users not shown)
Line 1: {{Hacking OpenHatch}} This page is now included in our project package, and is automatically generated by sphinx at openhatch.readthedocs.org: [http://openhatch.readthedocs.org/en/latest/advanced/deployment.html Deployment] ~~This is a quick-and-dirty page explaining how to deploy new versions of the OpenHatch code.~~ ~~== Prerequisites ==~~ * You must be part of the [[Login team]] (so your SSH key is available in Gitorious and you're in the openhatch-committers group, and also that your SSH key is in the deploy@linode.openhatch.org account's .ssh/authorized_keys) * You must be at a computer with that SSH key * Deploying takes about 3 minutes, maybe less if things go well. ~~== Here's what you do ==~~ * Make sure .git/config says that the ''url'' for ''origin'' is: ~~git@gitorious.org:openhatch/oh-mainline.git~~ * <code>git fetch</code> # get the latest * <code>git checkout origin/master -b deploy_me</code> # create a deploy_me branch * Then get the patch file with e.g. wget, and do * <code>git am /path/to/the/patch.file</code> # Import the patch into current branch, probably called deploy_me * Then "git log" and sanity-check it * If you like it, do ~~cd mysite~~ ~~./scripts/deploy~~ * Sometimes the deploy script takes two attempts for no good reason. * It's really important to make the separate branch so that you don't accidentally push random local work into the live site.