...
|
...
|
@@ -18,9 +18,9 @@ repository is named `your_username.github.com` or `your_organization.github.com`
|
18
|
18
|
git remote add origin (your repository url)
|
19
|
19
|
git push origin master
|
20
|
20
|
|
21
|
|
- # If you're using Github user or organization pages,
|
22
|
|
- # rename the master branch to source and then push
|
23
|
|
- git branch -m master source
|
|
21
|
+ # Next, if you're using Github user or organization pages,
|
|
22
|
+ # Create a source branch and push to origin source.
|
|
23
|
+ git branch source
|
24
|
24
|
git push origin source
|
25
|
25
|
|
26
|
26
|
|
...
|
...
|
@@ -40,7 +40,7 @@ Next, setup an [RVM](http://beginrescueend.com/) and install dependencies.
|
40
|
40
|
|
41
|
41
|
rake generate # Generates your blog into the public directory
|
42
|
42
|
rake watch # Watches files for changes and regenerates your blog
|
43
|
|
- rake preview # Watches, regenerates, and mounts a webserver at http://localhost:4000
|
|
43
|
+ rake preview # Watches, and mounts a webserver at http://localhost:4000
|
44
|
44
|
|
45
|
45
|
Jekyll's built in webbrick server is handy, but if you're a [POW](http://pow.cx) user, you can set it up to work with Octopress like this.
|
46
|
46
|
|
...
|
...
|
@@ -48,29 +48,28 @@ Jekyll's built in webbrick server is handy, but if you're a [POW](http://pow.cx)
|
48
|
48
|
ln -s /path/to/octopress
|
49
|
49
|
cd -
|
50
|
50
|
|
51
|
|
-Now you'll just run `rake watch` and load up `http://octopress.dev` instead.
|
|
51
|
+Now that you're setup with POW, you'll just run `rake watch` and load up `http://octopress.dev` instead.
|
52
|
52
|
|
53
|
53
|
## Writing A Post
|
54
|
54
|
|
55
|
|
-While running `rake preview` or `rake watch`, open a new terminal session and start a Hello World post.
|
|
55
|
+Create your first post.
|
56
|
56
|
|
57
|
57
|
rake post['hello world']
|
58
|
58
|
|
59
|
|
-This will create a new post named something like `2011-06-17-hello-world.markdown` in the `source/_posts` directory.
|
|
59
|
+This will put a new post in source/_posts with a name like like `2011-07-3-hello-world.markdown` in the `source/_posts` directory.
|
60
|
60
|
Open that file in your favorite text editor and you'll see a block of [yaml front matter](https://github.com/mojombo/jekyll/wiki/yaml-front-matter)
|
61
|
61
|
which tells Jekyll how to processes posts and pages.
|
62
|
62
|
|
63
|
63
|
---
|
64
|
64
|
title: Hello World
|
65
|
|
- date: 2011-06-17 14:34
|
|
65
|
+ date: 2011-07-03 5:59
|
66
|
66
|
layout: post
|
67
|
67
|
---
|
68
|
68
|
|
69
|
|
-Now, go ahead and type up a sample post, or use some [inspired filler](http://baconipsum.com/). Save and refresh your browser, and you
|
|
69
|
+Now beneath the yaml block, go ahead and type up a sample post, or use some [inspired filler](http://baconipsum.com/). If you're running the watcher, save and refresh your browser and you
|
70
|
70
|
should see the new post show up in your blog index.
|
71
|
71
|
|
72
|
|
-Octopress does more than this though. Check out [Blogging with Octopress](#include_link) to learn about cool features which
|
73
|
|
-help make blogging easier and more beautiful.
|
|
72
|
+Octopress does more than this though. Check out [Blogging with Octopress](#include_link) to learn about all the different ways Octopress makes blogging easier.
|
74
|
73
|
|
75
|
74
|
## Configuring Octopress
|
76
|
75
|
|
...
|
...
|
@@ -106,18 +105,18 @@ If you're using Github user or organization pages, clone the repository `git@git
|
106
|
106
|
|
107
|
107
|
# For Github project pages:
|
108
|
108
|
git clone git@github.com:username/project.git _deploy
|
109
|
|
- rake init_deploy[gh-pages]
|
|
109
|
+ rake config_deploy[gh-pages]
|
110
|
110
|
|
111
|
111
|
# For Github user/organization pages:
|
112
|
112
|
git clone git@github.com:username/username.github.com _deploy
|
113
|
|
- rake init_deploy[master]
|
|
113
|
+ rake config_deploy[master]
|
114
|
114
|
|
115
|
115
|
# Now to deploy, you'll run
|
116
|
|
- rake push
|
|
116
|
+ rake deploy
|
117
|
117
|
|
118
|
|
-The `init_deploy` rake task takes a branch name as an argument and creates a [new empty branch](http://book.git-scm.com/5_creating_new_empty_branches.html), adds an initial commit, and pushes it to the origin remote.
|
119
|
|
-This prepares your branch for easy deployment. The `rake push` task copies the generated blog from the `public` directory to the `_deploy` directory, adds new files, removes old files, sets a commit message, and pushes to Github.
|
120
|
|
-Then Github will queue your site for publishing (which usually occurs within minutes).
|
|
118
|
+The `config_deploy` rake task takes a branch name as an argument and creates a [new empty branch](http://book.git-scm.com/5_creating_new_empty_branches.html), and adds an initial commit.
|
|
119
|
+This prepares your branch for easy deployment. The `rake deploy` task copies the generated blog from the `public` directory to the `_deploy` directory, adds new files, removes old files, sets a commit message, and pushes to Github.
|
|
120
|
+Github will queue your site for publishing (which usually occurs instantly or within minutes if it's your first commit).
|
121
|
121
|
|
122
|
122
|
## License
|
123
|
123
|
(The MIT License)
|