4 ms·

I'd be curious to hear someone from Bocoup describe how this boilerplate fits in when you're already using a web framework. In Rails, or Django, or whatever, w

I'd be curious to hear someone from Bocoup describe how this boilerplate fits in when you're already using a web framework. In Rails, or Django, or whatever, wouldn't you want to use the built-in JavaScript folder structure and asset building strategy?

tbranyen 15y ago
You would modify the folder structure of the boilerplate to accommodate the framework. Assuming your framework does asset building as well, you can just delete the build folder.
- pacomerh 15y ago
  Yeah, boilerplate structures based on the most popular frameworks would be cool small project and time saver. I'm gonna adopt this idea.
danso 15y ago
Codebrew has its own rails-backbone gem: https://github.com/codebrew/backbone-rails https://github.com/codebrew/backbone-rails
- ryanfitz 15y ago
  I'm the author of that gem. My goal with it is to really just help people get up and running with rails & backbone as quickly as possible. There are no best practices built in and I try to avoid adding any extra features that aren't needed for getting started. I'm sure you could use rails-backbone to help get off the ground and then read over the snippets from backbone-boilerplate to see where to go from there.
ryanfitz 15y ago
I'm not from Bocoup, but I want something like this to build, test, deploy the client portion of my apps and then proxy api calls to backend services.
goblin89 15y ago
Not from Bocoup, and can't speak for Rails, but Django mostly does not care about that. I started using Brunch with Django recently, by simply putting it (sans bundled index.html) into `$PROJECT/client-side` directory and specifying the build folder as a primary static files directory. Then I run `brunch watch` in parallel with development server. The same could be done with boilerplate, it seems.
xmlninja 15y ago
Always better to keep frontend app and backend app separated. rails/django should only output json.

tbranyen 15y ago

You would modify the folder structure of the boilerplate to accommodate the framework. Assuming your framework does asset building as well, you can just delete the build folder.

pacomerh 15y ago
Yeah, boilerplate structures based on the most popular frameworks would be cool small project and time saver. I'm gonna adopt this idea.

danso 15y ago

Codebrew has its own rails-backbone gem: https://github.com/codebrew/backbone-rails https://github.com/codebrew/backbone-rails

ryanfitz 15y ago
I'm the author of that gem. My goal with it is to really just help people get up and running with rails & backbone as quickly as possible. There are no best practices built in and I try to avoid adding any extra features that aren't needed for getting started. I'm sure you could use rails-backbone to help get off the ground and then read over the snippets from backbone-boilerplate to see where to go from there.

ryanfitz 15y ago

I'm not from Bocoup, but I want something like this to build, test, deploy the client portion of my apps and then proxy api calls to backend services.

goblin89 15y ago

Not from Bocoup, and can't speak for Rails, but Django mostly does not care about that. I started using Brunch with Django recently, by simply putting it (sans bundled index.html) into `$PROJECT/client-side` directory and specifying the build folder as a primary static files directory. Then I run `brunch watch` in parallel with development server. The same could be done with boilerplate, it seems.

xmlninja 15y ago

Always better to keep frontend app and backend app separated. rails/django should only output json.