Sample Rails app using vendored engines and gems to provide functionality
Ruby JavaScript HTML CSS Shell
Latest commit 7fe6d7f Jul 28, 2015 @shageman Merge pull request #23 from bundacia/readme-fix
Fixing link to Pivotal Labs blog posts.

Thanks, Trevor!
Permalink
Failed to load latest commit information.
bin Added missing rails executable Mar 12, 2014
components Reenabling one build per component on travis-ci. Mar 11, 2015
config Move rails application back to root to make heroku deployment work again Mar 12, 2014
db Move rails application back to root to make heroku deployment work again Mar 12, 2014
log Move rails application back to root to make heroku deployment work again Mar 12, 2014
public Move rails application back to root to make heroku deployment work again Mar 12, 2014
script Move rails application back to root to make heroku deployment work again Mar 12, 2014
spec Move rails application back to root to make heroku deployment work again Mar 12, 2014
vendor Move rails application back to root to make heroku deployment work again Mar 12, 2014
.gitignore Ignore all sqlite files Sep 5, 2014
.rspec Added spec. Sep 12, 2012
.ruby-gemset Depend on publicly available event counter Apr 4, 2013
.ruby-version Set ruby-version to just "2.1.0" Sep 5, 2014
.travis.yml Reenabling one build per component on travis-ci. Mar 11, 2015
Gemfile Using bundler’s path option to better specify dependencies. Jan 12, 2015
Gemfile.lock Using bundler’s path option to better specify dependencies. Jan 12, 2015
MIT-LICENSE Moved a little bit too much... Feb 12, 2014
README.md Fixing link to Pivotal Labs blog posts. Jul 27, 2015
Rakefile Move rails application back to root to make heroku deployment work again Mar 12, 2014
build.sh Pin build.sh runs' working directory. Jan 16, 2015
config.ru Move rails application back to root to make heroku deployment work again Mar 12, 2014
migrate_and_prepare_all.sh Move rails application back to root to make heroku deployment work again Mar 12, 2014
test.sh Reenabling one build per component on travis-ci. Mar 11, 2015

README.md

The Next Big Thing Build Status Dependency Status Code Climate

What is this?

A full-fledged portal to announce the next big thing! Jumpstart the PR campaign for your next big thing by standing on the shoulder of a giant: The next big Thing!!

What is this really?

A sample project showcasing the use of unbuilt Rails Engines and Gems. The entire app has been developed using TDD - follow the commits to see the parts evolve. Current state:

  • Teaser provides the web page one sees when running the the_next_big_thing server. It depends on all the other engines.
  • Annoyance contains a service that given a number will give an indication of how annoying that number is.
  • EmailSignup provides a service allowing the storage of email addresses.
  • EventCounter provides a service that can count for any object how many times a particular action has happened.
  • The main Rails application does not contain any application code: it does not even have an app directory. It is soley responsible for encapsulating and mounting the engine in the right place.

Resources on component-based Rails applications

Twitter hashtag: #cbra - https://twitter.com/hashtag/cbra

Blog posts:

Past presentations by Ben Smith and me (mostly on this topic)

The book I am writing

Running the test suite

git clone https://github.com/shageman/the_next_big_thing.git
cd the_next_big_thing
./build.sh

Contributing

I highly appreciate it!

Fork, pull, create, commit, push, request pull.

License

Copyright (c) 2012-2013 Stephan Hagemann
twitter.com/shageman
%w(stephan.hagemann gmail.com) * "@"

Released under the MIT license. See MIT-LICENSE file for details.