tapicero.git - [tapicero]

Age	Commit message (Collapse)	Author
2013-12-19	add design docs on db creation, use Pathname	Azul
	Pathname makes dealing with files easier than String. Tapicero will look for design documents in design directory in the tapicero path for now.
2013-12-19	Version 0.2.0: use CouchRest::Changes	Azul
	This also changes the format of the config file. Please make sure to adjust it.
2013-11-28	rescue from 404 when destroying db	Azul
	Also logging per user db creation and destruction if they happen.
2013-11-28	make sequence accept all kinds of json	Azul
	bigcouch uses arrays for sequence: http://mail-archives.apache.org/mod_mbox/couchdb-user/201301.mbox/%3CCABvT1DEGDCJyvEuFsNJZbXi_NJwJna8NHDnQvpr2h532s0V18g@mail.gmail.com%3E So we should not expect them to be integers. Still have to catch the empty file situation in a meaningful way though.
2013-11-27	ignore design document changes - do not trigger callbacks then	Azul
	tapicero should create per user databases when a user is created and destroy them when that user is destroyed. However it should not attempt the same if design docs are created or destroyed.
2013-11-18	use our logger - not just puts	Azul

2013-11-18	delete user db's on user deletion.	Azul

2013-11-18	fix issues with storing and retrieving the sequence	Azul
	.to_i makes retrieving the sequence more robust - in particular if the file content was not meaningful. store_seq should also be called if it was a destroy action.
2013-11-18	add a hook for reacting on user deletion.	Azul

2013-09-25	log to file or syslog instead of STDOUT	Azul

2013-09-16	refactor - separate reading the last sequence from initialize	Azul

2013-09-12	use CouchRest::Database#changes, store and retrieve seq	Azul
	This commit bundles a few different changes: * we now use the CouchRest::Database#changes stream instead of our own * we store and read the last sequence number so on a restart we can start where we left * we now have a UserDatabase class rather than the CouchDatabaseCreator. It also knows about it's name and we create an instance of it per database we want to create. It's also more flexible when the databases already exist.
2013-09-11	use password and username from the config file	Azul

2013-09-11	write _security to fresh couch	Azul

2013-09-11	create couch dbs as users are created	Azul

2013-09-10	use our own JsonStream and a created callback in CouchChanges	Azul

2013-09-10	bringing over couch_changes from leap_ca including tests	Azul

2013-09-10	copying over skeleton from leap_ca which worked similarly	Azul