The generation hasn't been automated yet, I am currently doing these pushes manually because they're very brittle due to external/clean content (the md files). Yes, a Gemfile would be great to have. Last I tried making this work on something newer than 1.8.7 I got a bunch of parsing errors down in the weeds. I gave up chasing down the real issue since I actually wanted to push an update. I can take another stab at it.
-----Original Message----- From: crowbar-bounces On Behalf Of Adam Spiers Sent: Monday, November 25, 2013 12:01 PM To: crowbar Subject: Re: [Crowbar] What is Crowbar exactly? Ah, I see. Is the generation automated? If so, how and where? There should be a Gemfile to handle the gems required. And we should really get this working on Ruby 2.0.0 or 1.9.3 at least, since 1.8.7 is absolutely ancient now. Simon Jakesch (simon_jake...@dell.com) wrote: > The procedure to update the site is explained in: > https://github.com/crowbar/crowbar.github.com/blob/master/README.md. > All edits should be done at raw.crowbar.github.com, edits performed to > crowbar.github.com will be overwritten. The "turning off Jekyll" > commit message refers to the dynamic site generation on github.com. > Since we're using plugins (to pull content from the various repos) > we're no longer able to use Github's Jekyll process, but instead have > to generate the site outselves before uploading. _______________________________________________ Crowbar mailing list Crowbar@dell.com https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/ _______________________________________________ Crowbar mailing list Crowbar@dell.com https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/
