tapicero.git - [tapicero]

Age	Commit message (Collapse)	Author
2015-03-17	added support for tmp_users db. not backward compatible with prior config ↵	elijah
	files (seq_file changed to seq_dir)
2014-12-16	restore older "Creating database" capitalization.version/0.6	elijah

2014-12-14	try to create the db many times until it exists	elijah

2014-11-30	set version to 0.6	elijah

2014-11-30	do not log an error if db or design docs already exist (another tapicero ↵	elijah
	created it).
2014-09-23	Don't die when couchdb gets restarted (closes #6065)	elijah

2014-06-27	minor: lot's of small fixes to make replication work	Azul

2014-06-26	minor: include username in save_url	Azul

2014-06-23	initial take on replication	Azul

2014-03-11	make warnings more readable to nagios - #5247	Azul

2014-02-04	Merge pull request #10 from azul/refactor/user-database	jessib
	Refactor/user database
2014-02-04	Merge pull request #9 from azul/test/integration-with-travis	jessib
	Test/integration with travis
2014-02-04	Version 0.4.00.4.0	Azul
	minor changes improving stability
2014-02-04	prevent 409s and 412 and reraise them in tests	Azul
	Including tests that ensure this
2014-02-04	refactor: moved prepare and destroy into user_event_handler	Azul

2014-02-04	refactor: separate user event handler	Azul

2014-02-04	refactor: init user_database with a couchrest db	Azul

2014-02-04	hand config files on the command line to the daemon	Azul

2014-01-14	properly refer to logger in user_database	Azul

2014-01-14	fix UserDatabase#prepare	Azul

2014-01-11	Revisions sometimes start at 2 - work around this	Azul
	This is an intermediate fix. There's a user record that never had it's database created. The first time it shows up in the changes feed the revision starts with 2-. Not sure why this is. But we loose this user record if we rely on CouchRest::Changes.created which checks for a revision starting with 1-.
2014-01-03	make logging more precise	Azul
	* do not log the SystemExit after the fork * log error classes alongside messages * unify logging in retry_request_once * debug now logs every step * info has one message per user created * warn only logs errors during the actions * error only logs crashes
2014-01-03	Version 0.3.2 - staying alive0.3.2	Azul
	This version mainly improves the stability and should keep tapicero from dying too early. * couchrest_changes 0.0.5 will resume if the connection died. * lock yajl version to 1.1.0 - 1.2.0 requires mkmf on the server * retry couch requests in case they fail * log all crashes
2014-01-03	better debug loggin, sleep before retrying	Azul

2014-01-03	retry couch requests once	Azul
	Couch sometimes responds with 500 or so. Often this is temporary. Let's retry once and log the error instead of dying.
2013-12-22	Version 0.3.1 with new flags --run-once, --rerun and --overwrite-security0.3.1	Azul
	--run-once will exit once all current changes have been processed --rerun will process all users again even those that were processed before --overwrite-security will overwrite security for user databases even if it has been set before.
2013-12-20	Version 0.3.0: include design docs on created databases0.3.0	Azul

2013-12-20	proceed if design docs are already there	Azul
	We'll add a flag to overwrite designs and / or security later. For now just make sure this does not crash tapicero.
2013-12-20	add design docs to be included in each user database	Azul
	Also strip the .json extention because soledad does not expect it
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