That's right. There's work in the trunk to break that out a bit, but
the frontend is based around a separate sql database.
- Luke
On Jun 11, 2008, at 2:24 PM, Randall Leeds wrote:
Even after doing these things, websetup.py in melkjug.melkjug.lib
still makes calls against the sql server as does melkjug.lib.security
Is this necessary with potato, e.g. sql still stores user info?
On Wed, Jun 11, 2008 at 1:58 PM, Luke Tucker <[EMAIL PROTECTED]>
wrote:
Hey,
Should probably add a wiki page on it, but there are a couple of
variables in development.ini that are intended to enable the use of
the alternate 'potato' backend:
1) comment out melk.silo.monolith lines:
# melk.silo.monolith.db.url = mysql://melkjug:[EMAIL PROTECTED]/
monolith
# melk.silo.monolith.db.pool_recycle = 3600
# melk.silo.monolith.db.echo = true
2) uncomment the melk.silo.potato.db.url line and point it to
wherever is sensible:
#
# This configures the CouchDB backend
# (Experimental!)
#
melk.silo.potato.db.url = http://localhost:5984/melk_tater
3) enjoy!
- Luke
--
Archive:
http://www.openplans.org/projects/melkjug/lists/melkjug-development-list/archive/2008/06/1213207122302
To unsubscribe send an email with subject unsubscribe to [email protected]
. Please contact [EMAIL PROTECTED] for
questions.
!DSPAM:4013,48501b0b201021849620573!
