vidkun / autotrakr

An app for keeping track of vehicles, their parts, modifications, service/maintenance records, etc.

README

This project is every bit as much to solve my own problem as it is a means for me to learn and explore new technologies, such as mongodb, background workers (sidekiq), and haml. It is also an opportunity for me to strengthen my skills in other areas such as testing, coffeescript/javascript, and other rails patterns.

I enjoy wrenching on my own vehicles and have yet to find a decent solution for enthusiasts to track and manage their personal vehicles. Every solution so far is geared more towards companies that need to manage their fleet of business vehicles.

Autotrakr is intended to allow individuals to add vehicles to their garage and track the maintenance of those vehicles and build a profile to show off these vehicles. Users can add photos to their vehicle records, track what parts and upgrades have been added to the vehicle, add service records to track routine maintenance, add service reminders based on customizeable service intervals, and maintain a list of consumable products perferred for routine maintenance such as part numbers for: oil filters, air filters, fuel filters, different fluids, etc.

Feel free to submit pull requests or open issues if you have any.

autotrakr's Issues

To model or not to model?

A 'garage' is a user's public profile and main starting point. Vehicles are added to a user's garage and then the garage show view displays a list of all the user's vehicles for further drill down.

The question then, is should garage be a model that has_many vehicles and belongs_to a user with vehicles belongs_to a garage? Or should garage simply be a controller with a show view that pulls in all vehicles for a user (vehicle belongs_to user and user has_many vehicles)?

A benefit of using a model is that a user's garage would be a document that contains all vehicle documents for a user. A single DB read would load in all of the user's vehicles for display. Not sure if pulling in the vehicles via only a garage controller would result in a single read regardless of number of vehicles as well. Though, I am leaning that way.

Doesn't make much sense to have an entire model for a garage just to handle collecting the user's vehicles.

I do know that I don't want to embed the vehicles into the user's document in order to achieve the single read load listed as a benefit of a garage model. This would result in reading in all of the user's vehicles every time the user instance is loaded (i.e. login) which would be horrible.