Deploying to github pages via Travis #940

Open
darvin opened this Issue Jan 13, 2013 · 6 comments

Comments

Projects
None yet
4 participants
@darvin

darvin commented Jan 13, 2013

I'm using this workflow:

Basically, I added this .travis.yml to root of by blog and used this method for travis encoding of my ssh github key (for pushing to github pages). No octopress modifications necessary. This method allows user to edit source code of blog (add post, edit post, edit settings, config, wharever) just via browser (like in prose.io or just in Github web editor.

Maybe it nice feature to have in octopress out of box? like in rake setup_github_pages or something?

@imathis

This comment has been minimized.

Show comment Hide comment
@imathis

imathis Jan 13, 2013

Owner

This is exactly the sort of thing I'd like to be doing in Octopress. Thanks for your work on this. I'll look into it.

Owner

imathis commented Jan 13, 2013

This is exactly the sort of thing I'd like to be doing in Octopress. Thanks for your work on this. I'll look into it.

@darvin

This comment has been minimized.

Show comment Hide comment
@darvin

darvin Jan 14, 2013

the thing is - github now supports jekyll sites natively. Octopress is framework on top of jekyll. Is there any possibility to pack whole Octopress business and plugins to be compatibly with plain jekyll? This way we could deploy stuff just by storing it on github.

darvin commented Jan 14, 2013

the thing is - github now supports jekyll sites natively. Octopress is framework on top of jekyll. Is there any possibility to pack whole Octopress business and plugins to be compatibly with plain jekyll? This way we could deploy stuff just by storing it on github.

@imathis

This comment has been minimized.

Show comment Hide comment
@imathis

imathis Jan 14, 2013

Owner

@darvin GitHub won't allow plugins or other external code to be run. Octopress ads a lot to Jekyll that Github just won't do.

Owner

imathis commented Jan 14, 2013

@darvin GitHub won't allow plugins or other external code to be run. Octopress ads a lot to Jekyll that Github just won't do.

@drgomesp

This comment has been minimized.

Show comment Hide comment
@drgomesp

drgomesp Jan 15, 2013

This is incredible! Thank you for this contribution!

This is incredible! Thank you for this contribution!

@floydpink

This comment has been minimized.

Show comment Hide comment
@floydpink

floydpink Jan 18, 2013

Contributor

@darvin : I was thinking about trying to do something like this with Travis-CI only this morning.

Also, if the commit message has [ci skip] in it somewhere, Travis skips building that commit as mentioned here. Maybe that's something that could be done to the commit message within rake deploy.

Anyways, awesome stuff! Thank you...

Contributor

floydpink commented Jan 18, 2013

@darvin : I was thinking about trying to do something like this with Travis-CI only this morning.

Also, if the commit message has [ci skip] in it somewhere, Travis skips building that commit as mentioned here. Maybe that's something that could be done to the commit message within rake deploy.

Anyways, awesome stuff! Thank you...

@floydpink

This comment has been minimized.

Show comment Hide comment
@floydpink

floydpink Jan 28, 2013

Contributor

I implemented this successfully with a couple of tweaks to @darvin's process above. The gist is:

  • reverted _config.yml in the before_script after rake setup_github_pages (necessary for blogs published to a custom domain)
  • Rakefile edited to append [ci skip] to the commit message (to skip second ci-build)
  • modified the script to generate the travis-encrypted secure key, to match the current version's travis encrypt syntax

The details have been posted on my blog.

Contributor

floydpink commented Jan 28, 2013

I implemented this successfully with a couple of tweaks to @darvin's process above. The gist is:

  • reverted _config.yml in the before_script after rake setup_github_pages (necessary for blogs published to a custom domain)
  • Rakefile edited to append [ci skip] to the commit message (to skip second ci-build)
  • modified the script to generate the travis-encrypted secure key, to match the current version's travis encrypt syntax

The details have been posted on my blog.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment