Neat project. A couple code-reviewish notes:<p>* why use protected_attributes in an new Rails 4 project? I'm curious what motivated this decision.<p>* if you're destroying records, you'll want to look into using the :dependent option to has_many to make sure you clean things up. However, you may want to carefully consider where in the app "deletion" actually makes sense; anything that winds up in an accounting system probably shouldn't be deletable at all.<p>* get the tests running. The version on Github has a controller test for "ZusersController" which doesn't appear to exist in the application...<p>* a minor thing, but it'll drive future contributors crazy: hard tabs vs. soft tabs. Ruby code is usually two-space soft-tabs, but even if you don't agree with that at least be <i>consistent</i>. There are files on GH that are a riot of mixed tabs (configurations_controller.rb is a notable example) and nobody's got time for that.<p>I'm not the best at catching replies on HN, but ping me on Github (same username) if you want to discuss further.
I found this project really interesting. Forked it. It might be interesting to create platforms like this for the very commmon uses-cases: ecommecrce, blogging, CMS. Currently there are solutions for all this use cases in the rails community but imo they are pretty directed. I mean, they are "difficult" to modify. I would like something like rails composer where you can configure the basic elements of the platform without custom generators.
This is something I'm 100% behind. As a developer who works integrating with point of sales systems this is an industry ripe for disruption. The pain of integrating is killing innovation in retail. Whether it will be open source or someone like square I look forward to an industry standard in the future.