4 ms·
I think you'll find that the code is very easy to get into and bend to whatever you want to do. I'll toss more details up on the site, soon, though, so hopeful
by stympy 18y ago
I think you'll find that the code is very easy to get into and bend to whatever you want to do.
I'll toss more details up on the site, soon, though, so hopefully that will help give you a better feel for it.
- ericb 18y agoI already built logon/user accounts code for my app. Does this require your app's user code?
- stympy 18y agoI just updated the site with more details about the implementation. If you are using restful_authentication, it may be as easy as just making 3 one-line changes to your current user code (lib/authenticated_system.rb and app/models/user.rb), depending on how my notion of an Account lines up with how you're managing your customers.
- ericb 18y agoSounds promising. Would this be able to support a scheme like this: Rent n units at price y for x hours, where dollars per y-hour is dependent on the number of units n(volume discounts)? Show the user an interface with their current unit-hours and let them draw down against it?
- stympy 18y agoUh, I guess so... if you implement it. :) Kidding aside, you can do whatever you want on top of the base application -- it's a standard Rails app, after all. But what you get "out of the archive" is a bog-standard customer pays $x/mo for access to the app which has some limits based on the value of x, and the limits are up to you to implement (aside from the included one, which limits the number of users that can be associated with a customer's account).