Org-octopress has a setting called org-octopress-setup-file that points to your blog-specific information. It references this file when it exports your org-mode source file to the HTML file it that Jekyll uses to generate your GitHub pages site.

When you create a new post, Org-octopress fills in a skeleton org-mode file that you use to write in to compose your blog post. When it does this it fills in the path for a setting at the top:

#+SETUPFILE: <path-to-setupfile>

For this to work nicely, it is helpful to store your setup file a place that you can reference with a nice relative path on all the machines involved. In my case I used this:

~/.emacs.d/octopress-setupfile.txt

If I were maintaining multiple sites I would give the setup file for each site a unique name.

The scripts that set-up your site structure handles everything for you. However, if you clone your existing site onto a new machine, you must make sure that the following conditions are satisfied. In what follows site-root is the path to the main git repository on your local machine where the site is being maintained.

• <site-root> is a git repository with the following remotes:

  octopress   git://github.com/imathis/octopress.git (fetch)
  octopress   git://github.com/imathis/octopress.git (push)
  origin  <your-github-repository-path> (fetch)
  origin  <your-github-repository-path> (push)
  

• It has the source branch checked-out
• <site-root>/_deploy is a sub-directory that is maintained by Jekyll. It is also a git repository with the following remotes:

  origin  <your-github-repository-path> (fetch)
  origin  <your-github-repository-path> (push)
  

• It has the master branch checked-out.
• This _deploy directory is in the main repos .gitignore file.

So, when you want to set-up a secondary machine where you can maintain your site, you must manually checkout a copy of the repo into the _deploy sub-directory and make sure the master branch is checked-out.

One other note about this: If you get an error from Jekyll when it tries to deploy your site when it tries to push master -> master, you need to go into the _deploy sub-directory and do something like this:

git fetch origin
git rebase origin master
git push origin master