Add support for deploying to github pages about awestruct HOT 10 CLOSED

Github pages is jekyll-aware, but not awestruct-aware. And it won't ever be awestruct-aware without changes from the people at github. But I do think we can do something with git, a gh-pages root branch and a little magic.

from awestruct.

That's what I had in mind.

from awestruct.

This is done on master. Until we push a version > 0.2.15, you'll need to install the gem from source in order to use it.

from awestruct.

wow - sweet!

from awestruct.

Check out http://github.com/awestruct/github_pages for a simple example

from awestruct.

Hi Lance,

I followed instruction to publish from awestruct but it doesn't work. My repo is : https://github.com/agorava/agorava.github.com

It's intended to generate http://agorava.org but only get 404 github page. If I copy generated index.html from gh-pages to master it works.

Thanks for helping

from awestruct.

Antoine,

Awestruct can be split in two parts :

• the "_site" dir
• the rest

In the first, it's your generated website (HTML pages, CSS, etc...). In the second one, it's your code (HAML, SASS, Textile, YML, ...).

Since your repo is "agorava.github.com", your need to put the generated code (the one in "_site") in the master branch. You can put the rest on the develop branch (you can ignore the "_tmp" dir since it's only temp files). Doing so will publish the code at the following url : agorava.github.com (I think http://agorava.org is not possible in GithHub).

If your repo was having a different name, you would need a "gh-pages" branch. But since it follows the syntax "username.github.com", it's a particularcase where published files need to be in "master" branch.

See https://github.com/pauldijou/pauldijou.github.com for concrete example and the result is at http://pauldijou.github.com/ .

Regards.

from awestruct.

Antoine

Looks like you're all set now, based on Paul's response. Let me know if you run into further problems.

Lance

On May 1, 2012, at 12:30 AM, Antoine Sabot-Durand wrote:

Hi Lance,

I followed instruction to publish from awestruct but it doesn't work. My repo is : https://github.com/agorava/agorava.github.com

It's intended to generate http://agorava.org but only get 404 github page. If I copy generated index.html from gh-pages to master it works.

Thanks for helping

---

Reply to this email directly or view it on GitHub:
#91 (comment)

from awestruct.

Thanks Paul, Lance.
I came to the conclusion on my side : when site is at the root of the organization (i.e. http://agorava.gthub.com) gh-pages branch is ignored and master branch is used. Now http://agorava.org is up (1 page site : victory ! ;-) )

However I still have an issue with awestruct deployment. In http://agorava.github.com I created a develop branch to keep source of my site in it and have master branch only containing the generated site. In order to do this I created the following _config/site.yml

profiles: 
  production: 
    base_url: http://agorava.github.com
    deploy: 
      host: github_pages
      branch: master

When I do a awestruct -P production --deploy It does nothing in master branch and keeps publishing in gh-pages. For the moment I fixed this issue manually by copying gh-pages files in master. I'm working with awestruct version 0.2.18.
Before I create a ticket for ths issue could you tell me if I'm doing something wrong ? Thank you.

from awestruct.

Antoine

Support for publishing your site on the master branch is not yet available in a release. That was added after 0.2.18 and should be in the next release. In the meantime, it's pretty easy to build and install awestruct from source.

$ git clone git://github.com/awestruct/awestruct.git
$ cd awestruct
$ rake install

That should provide you with an awestruct 0.2.19 gem locally that you can use to generate your site on the master branch.

Lance

from awestruct.