Deployment (moved)
This is a page about improving or modifying OpenHatch.
We call that "Hacking OpenHatch," and there is a whole category of pages about that.
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
git fetch# get the latestgit checkout origin/master -b deploy_me# create a deploy_me branch- Then get the patch file with e.g. wget, and do
git am /path/to/the/patch.file# 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.