Launch Site Commuter
This is an entry in the 2012 Rails Rumble. After checking it out, we encourage you
to leave feedback and then take a look at the hundreds of other amazing entries.
By "247 Studio"
"Commuter" is the codename for our application created to provide an easy solution for managing car rides to and from work.
By performing searches based on origin, destination, and desired timeframe, a user can sift through the list of available carpools and pick the most desirable match. This decision may be based on what seat is available in a given car (like choosing a seat on an airline), or based on the vicinity of either endpoints of the commute, musical preferences of the other would-be passengers, past ratings ... as well as things like "Does this driver smoke?" or "Does she wear too much perfume?"
If you are in either of the driver/passenger roles and can establish a repeatable schedule, you can avoid having to manually search for rides on a day-to-day basis (and maybe even "Favorite" your new friends). Plus, using integrations with external APIs forthcoming, you can be notified by Email, SMS, App notification regarding traffic/weather updates as they pertain to your regular route.
In the future, we will be allowing passengers to pitch in nominal amounts toward the designated driver, allowing them to share parking, toll, gas expenses involved with carpooling.
For testing, there isn't much seeded to the database unless you designate Emeryville as your origin and SF-Financial District as your destination (although any SF location should work as well.)
Interested in seeing what was used to build this application? Resources may include things like open source libraries, third party APIs, and icons.
We used PivotalTracker to brainstorm the myriad of potential tasks and stories involved with the project, but it was most useful in weeding out the too-far-off-in-the-future features which we've tabled for the sake of expe...
We used PivotalTracker to brainstorm the myriad of potential tasks and stories involved with the project, but it was most useful in weeding out the too-far-off-in-the-future features which we've tabled for the sake of expediency.
Our team developed in our apartment on Mac OS X's, using Illustrator for Mockups, Twitter Bootstrap for general layout templating (as well as a few components here and there). Our environments in both development and production use the MySQL database, and our ruby/gems are managed by RVM. Our Gemfile includes many libraries, although it's likely something like 90% of them weren't even utilized within these 48 hours. Included in those gems are two or three gems I had open-sourced on GitHub in the past, but I may not even have had the opportunity to utilize those either.
What gems I do know we utilized include twitter-bootstrap-rails, modernize-rails, devise, capistrano, and asset-pipeline-related gems.
Oh. Copied the deploy script from RR organizers for the linode deploy.