It has only been a couple of days using Octopress and Pow* but I am already sold. For offline blogging, GitHub Pages support, a great set of standard Markdown-ish driven Plugins, etc… the workflow is great. There are a few things that I am missing like:
My Missing Octopress Items:
- Image Auto Thumb-nailing
- Image Popups from those Thumbnails
- Post Staging (The ‘published: false’ yaml front matter is a start but….)
- Auto source directory version control
That last one was my highest priority. When you run the Octopress GitHub Pages setup, it configures the deployment repo (XXXXXX.github.io), but you still need to backup and/or version control the ‘source’ directory.
Here is my quick way of doing this using the deployment repo.
- Add a source branch your your “XXXXXX.github.io” repo
- Set your local source directory as a single branch of that repo
- Commit and Push after you do a rake deploy
So lets add a source branch to your GitHub Page repo: Note: This is my quick way (ie. hackie) to get an EMPTY new remote branch into an existing repo. If someone knows a better way, I’d love to hear it.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 |
|
You already have an existing source directory and if you did not change the _config.yaml defaults is under your Octopress directory and those files need to be placed in this new source branch you just created.
1 2 3 4 5 6 7 8 9 10 11 12 |
|
Now you have two branches in your Pages repo. master will be your deployed/published blog pages and source will be the content Octopress uses to create those pages.
Now, anytime you need to backup work-in-progress source changes or after you you do a rake deploy you can just do this:
1
|
|
I’ll be including this in the Github Page deploy plugin in the future so everytime I publish (deploy) I will also get a matching commit to the source branch…. But that and the other items on the Todo list will have to wait till later… ;-)
- Pow is a zero-config Rack server for Mac OS X : Watch Me