I'm always willing to take suggestions. We've expanded on the basics in the "unstable" branch - mostly focusing on adding a pure REST interface, which Rajesh has done a wonderful job with. It does have it's own settings when using it standalone - it's a pretty straight-up Django application that way.
It's not much work to integrate it into your app straight off - like I said, that's actually where I personally started with the concept. I just thought it had more value separate :-) It's not super-particular about the database - just like any other Django application. -joe On Jan 30, 2008 3:22 PM, Tane Piper <[EMAIL PROTECTED]> wrote: > That sounds fantastic - I think we might look at integrating it into > the application as it's pretty vital (imagine having to wait for a 50 > or 100mb repository to clone!). > > If your interested, I'd be happy to provide some code back if we can > make any improvements. For example, we're using a forked version of > django-dbsettings and it would be very handy to put the settings to > control the application here, stuff like throttling, limits, etc. > > Does it have it's own settings file if it's using a SQLLite backend? > Would it be much work, or even worth it to integrate it into the > database within our app? Of course our app supports using SQLLite as > a DB option (especially good for our app running off a pen drive :) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
