Octopress/Octopress Workflow - Revision history

Admin at 07:49, 11 April 2014

2014-04-11T07:49:59Z

← Older revision		Revision as of 07:49, 11 April 2014
Line 38:		Line 38:
	</pre>		</pre>

	to pull all the changes. (Due to the layout of user pages, this will consist of the source branch, which contains the source code for generating the site's static content, as well as the master branch, which contains the live static content, in the ~~very confusingly-named~~ <code>~~source~~</code> directory.		to pull all the changes. (Due to the layout of user pages, this will consist of the source branch, which contains the source code for generating the site's static content, as well as the master branch, which contains the live static content, in the <code>_deploy</code> directory, which is ignored by git because of its leading underscore. (Tricky...) That's how you can have two repositories, one living in the other - the underscore in front of the name allows git to automatically ignore it.


	[[Category:Octopress]]		[[Category:Octopress]]

2014-04-11T06:25:27Z

← Older revision		Revision as of 06:25, 11 April 2014
Line 39:		Line 39:

	to pull all the changes. (Due to the layout of user pages, this will consist of the source branch, which contains the source code for generating the site's static content, as well as the master branch, which contains the live static content, in the very confusingly-named <code>source</code> directory.		to pull all the changes. (Due to the layout of user pages, this will consist of the source branch, which contains the source code for generating the site's static content, as well as the master branch, which contains the live static content, in the very confusingly-named <code>source</code> directory.


			[[Category:Octopress]]

2014-04-11T06:25:10Z

← Older revision		Revision as of 06:25, 11 April 2014
Line 1:		Line 1:
			Use this blog to help get two clones of Octopress up and running:

	http://blog.zerosharp.com/clone-your-octopress-to-blog-from-two-places/		http://blog.zerosharp.com/clone-your-octopress-to-blog-from-two-places/

			Now the routine workflow on either one looks like this:

			Let's do some stuff, like make a new post:

			<pre>
			bundle exec rake new_post['This is a new post']
			</pre>

			We'll edit some posts too. Now we want to turn all that markdown into blog pages. We do that by running generate:

			<pre>
			bundle exec rake generate
			</pre>

			Then we deploy all that static content to our live site:

			<pre>
			bundle exec rake deploy
			</pre>

			If we make changes to the site source code (i.e. the bundles, or the configuration, or whatever), then we would commit our changes to the source branch of our github (user) pages repository:

			<pre>
			git add .
			git commit -am "Commit changes to site source"
			git push origin source
			</pre>

			Once we're on the other machine, we will run

			<pre>
			cd charlesreid1.github.io/
			git pull
			</pre>

			to pull all the changes. (Due to the layout of user pages, this will consist of the source branch, which contains the source code for generating the site's static content, as well as the master branch, which contains the live static content, in the very confusingly-named <code>source</code> directory.

2014-04-10T00:33:01Z

Created page with "http://blog.zerosharp.com/clone-your-octopress-to-blog-from-two-places/"

New page

http://blog.zerosharp.com/clone-your-octopress-to-blog-from-two-places/