These look like remnants of previous design decisions, we don't actually
use the models or controllers anywhere. Later, if we do introduce saving,
configuration, etc. we can re-introduce the database, models, and
migrations, etc.
For now, this will make deployment easier and lightens up the code to
allow us to focus on the issues at hand
Closes #69 by removing dependency
Supports #65 by removing the models, views, w/ rails destroy scaffold Foo
Supports #66 by updating the README and removing complexity
These look like remnants of previous design decisions, we don't actually use the models or controllers anywhere. Later, if we do introduce saving, configuration, etc. we can re-introduce the database, models, and migrations, etc.
For now, this will make deployment easier and lightens up the code to allow us to focus on the issues at hand
Closes #69 by removing dependency Supports #65 by removing the models, views, w/
rails destroy scaffold FooSupports #66 by updating the README and removing complexity