jondot/graphene

dev env isn't working right?

Opened this issue · 3 comments

Hi, great project. I'm trying to add a couple features to it, but I'm having some problems getting the dev environment set up. I'm primarily a python guy without a lot of ruby experience so this is all new to me.

Anyways, it seems that when I run bundle exec guard start it picks up my changes and says it's recompiling build/index.js but that file is left full of sprockets include directives instead of the actual minified code.

Am I missing a step?

Thanks, Aaron

Hi,

I apologize if the build process is cumbersome, I've started testing an alternative on a separate branch (https://github.com/jondot/graphene/tree/rakep_assetpipeline) quite some time ago, but left it alone since I saw the current one is holding out OK.

The Holy Grail is to make a magical build process that doesn't care about what is already installed. But, the conclusion I'm getting at - I'm afraid no matter where one comes from (Python/Ruby/Node) there will always be some tooling to depend on; even if we drop to a simple Makefile (which I did in one of my other projects).

If this is still relevant, I'd love to help out if you can specify what of the steps you've already done, and what Ruby version you're on.

If anything, it urges me to complete a screencast I'm planning to better explain how to quickstart development on Graphene.

Thanks!

I did manage to get it working after much thrashing about, but now I'm trying to recreate it and having no luck. I've installed rvm and bundle installed and everything installs ok, but it still isn't processing the includes. I believe last time i got it working correctly was because I gem installed newer versions of guard and sprockets, but this time around I'm having no luck with that.

A screencast would be pretty huge, unfortunately, it seems like you may run into a lot of problems with different environments. I'm working on Ubuntu 12.04 and it seems like a lot of the packaged ruby stuff is not is a good way. Coming from python, I see similar problems with pip/easy_install/virtualenvs. It sometimes takes a lot of work to get to the point where the local environments are easy to work with. Anyways, I'll be excited to see what you can come up with. Also, if i get this figured out I'll be sure to update here.

agxs commented

I had a bit of trouble too. Had to add gem 'therubyracer' to the Gemfile to get Guard to rebuild the index.js file properly.