Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

rake generate not working #10

Closed
twiz- opened this Issue · 28 comments

8 participants

Tony Ramirez Zach Bruhnke limitingfactor WebVigilante Amir Sharif Anthony Wijnen Eric Theise Gaurav Jhaveri
Tony Ramirez

Running rake generate for a new post takes me to the jekyll man page. Is this a known issue or something on my end?

Zach Bruhnke
Owner

I just pushed a new version specifying the version of Jekyll, I'm going to re-factor the gem to use default rails layouts and look at the changes mojombo is making to Jekyll to make sure I include whatever I need to in the new version.

Now would be the time for feature requests

Zach Bruhnke
Owner

it does appear to have fixed the problem for me in a test repo I made just for this. let me know if that did not fix it for you, otherwise I'll go ahead and cose the issue

Zach Bruhnke zbruhnke closed this
Tony Ramirez

:+1: Everything is working as for me as expected outlined here. Amazing response time and tool, thanks for your work on this, will be using in multiple projects :)

limitingfactor

Rake generate is no longer working for me. I haven't created any blog posts in a while so I'm not sure when it stopped working but I'm using the latest bloggy version. Here's the output:

rake generate
Configuration from /Users/limitingfactor/Code/factor/config/jekyll/_config.yml
Auto-regenerating enabled: /Users/limitingfactor/Code/factor/config/jekyll -> ../../app/views/blog
[2013-08-13 21:04:33] regeneration: 1 files changed
[2013-08-13 21:04:33] regeneration: 1 files changed
[2013-08-13 21:04:33] regeneration: 1 files changed

The output looks correct but the only file that is generated/modified is the atom.xml. I'm using Rails 4 and Ruby 2.0.0-p247.

Zach Bruhnke
Owner

Sorry I missed these comments guys, been working hard on my startup.

I'll check it out either tonight or tomorrow

Zach Bruhnke zbruhnke reopened this
Anthony Wijnen

+1

Anthony Wijnen

Also running rails 4.0.0 & ruby 2.0.0 and the same issue is present whereby rake generate doesn't get completed. There's one more tidbit of debug info I gathered, i.e. when I force quit the rake task in console it spits out:

usr/local/rvm/gems/ruby-2.0.0-p247/gems/jekyll-0.12.1/bin/jekyll:259:in `sleep': Interrupt

Anthony Wijnen

arghh I really can't get it to work. Tried different versions of the gem, including branches of @jesseadams fork but no luck. Do you think you'll be tackling this one in the near future @zbruhnke? If not, are there any recommended alternatives for adding a blog to an existing rails app?

Don't mean to press, I'm just really looking to get this up and running in the coming weeks. Aside from the generate hick up it really seems to be the ideal tool for the job.

Thanks in advance.

Zach Bruhnke
Owner

@awijnen On it this weekend, going to get @jesseadams PR's merged in too then I'll take a look at what is going on here.

Really sorry for the delay all, Launching a new startup in a couple of weeks and my time has been almost non-existent!

Zach Bruhnke
Owner

Ok I'm seeing the same problem on a rails 4 app with Ruby 2, I'll get it figured out over the weekend! Thanks for your patience guys, my apologies for taking so long!

Zach Bruhnke
Owner

ok I bumped the gem to the newest version of jekyll and confirmed that rake generate should be working fine

also @awijnen make sure you set published to true when you create a new post.

I've also got plans to make the changes to allow default rails layouts as well, would you guys use that or is it not interesting to you guys?

Zach Bruhnke
Owner

@awijnen is this new update working for you? would love to closr out the issue and move onto working on bloggy 1.0 in the near future if so

Eric Theise

It's not working for me with ruby 2.1.0p0 and Rails 3.2.16. I still see the jekyll man page when I run bundle exec rake generate

Zach Bruhnke
Owner

is this with the updated gem I just released yesterday? @erictheise

Eric Theise

@zbruhnke, it was with the updated gem; since posting, I've upgraded my app to Rails 4 and it seems okay now. Apologies for the noise.

Zach Bruhnke
Owner

good to hear @erictheise anyone else have issues before I close this one?

Anthony Wijnen

@zbruhnke thanks a bunch for updating! Rake generate is no longer hanging, i.e. the console returns 'Generating.. done'. However it's still not adding the static html files in the public folder. Maybe I'm just doing something else wrong, that's unrelated.

Zach Bruhnke
Owner

@awijnen make sure that published is set to true in the posts directory.

screenshot:

screenshot 2014-01-25 15 35 36

Anthony Wijnen

should've caught that one myself :). anyway, it works like a charm now. thanks @zbruhnke !!!

Zach Bruhnke
Owner

glad its up and running for ya :) ... closing this issue!

Zach Bruhnke zbruhnke closed this
Gaurav Jhaveri

@zbruhnke I'm using Ruby 2.1 and Rails 4.0.2 and am still facing this issue. Explicitly specifying an older version of Jekyll (0.12.0) seemed to fix the issue for me.

Eric Theise

@Mutinix, if you've been using bloggy all along, upgrading to the latest version of the gem isn't going to be enough. The fix to lib/generators/jekyll/blog/templates/tasks/gen.rake.tt doesn't get picked up unless you regenerate your bloggy installation and get the revised tasks in place. Pretty sure that I solved my problem not by upgrading to Rails 4, but by starting a new app and copying my old configs and posts to the new installation after I'd done rails g jekyll:blog.

It's a PITA, but it's better than locking yourself into an old version of jekyll.

Eric Theise

@Mutinix, you'll also want to remove auto: true from your configs if you were using it (it'll generate deprecation warnings now) and use the autogenerate task @jesseadams created instead of the generate` task if you want to keep that behavior.

Gaurav Jhaveri

@erictheise This is perfect, thank you!

Gaurav Jhaveri

but by starting a new app and copying my old configs and posts to the new installation

@erictheise So you copied your old files in to the new app and proceeded to work with the new one? If that's not what you did, proceed to ignore everything after this.

What I did was follow your suggestion but rather than working with the new app, I copied the 2 tasks from lib/tasks in the new installation and replace their counterparts in the older one. I then removed auto: true and used autogenerate, just as you suggested. Finally, I removed the dummy app that I had created. Voila!

Once again, thank you for the help.

Eric Theise

@Mutinix, I think these are just two different ways of getting to the same solution. I tend to trust generators to know what they need to do, so for me it was easier to temporarily take out the files that I knew were mine, do a fresh generate of the bloggy install, then put my content and config settings back. It may well be that the only thing that changed was those two tasks.

If it's working for you and working for me, then hallelujah.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.