summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2014-01-14fix UserDatabase#prepareAzul
2014-01-13Merge pull request #8 from azul/bugfix/fix-for-revisions-starting-above-1jessib
Revisions sometimes start at 2 - work around this
2014-01-11Revisions sometimes start at 2 - work around thisAzul
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-03make logging more preciseAzul
* 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-03Version 0.3.2 - staying alive0.3.2Azul
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-03better debug loggin, sleep before retryingAzul
2014-01-03ensure we log all errorsAzul
2014-01-03retry couch requests onceAzul
Couch sometimes responds with 500 or so. Often this is temporary. Let's retry once and log the error instead of dying.
2014-01-02hotfix: use working couchrest_changes version and yajl 1.1.0Azul
yajl 1.2.0 required mkmf on the server which currently is not present
2014-01-02use latest couchrest_changes for more stabilityAzul
2013-12-22Version 0.3.1 with new flags --run-once, --rerun and --overwrite-security0.3.1Azul
--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-22Merge pull request #6 from azul/deploy-design-docsazul
Deploy design docs
2013-12-22Merge pull request #5 from azul/feature/use-couchrest-changesazul
Version 0.2.0: use CouchRest::Changes
2013-12-20Version 0.3.0: include design docs on created databases0.3.0Azul
2013-12-20proceed if design docs are already thereAzul
We'll add a flag to overwrite designs and / or security later. For now just make sure this does not crash tapicero.
2013-12-20add design docs to be included in each user databaseAzul
Also strip the .json extention because soledad does not expect it
2013-12-19add design docs on db creation, use PathnameAzul
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-19Version 0.2.0: use CouchRest::ChangesAzul
This also changes the format of the config file. Please make sure to adjust it.
2013-11-29Merge pull request #4 from azul/feature/more_robust_sequence_handlingjessib
Feature/more robust sequence handling
2013-11-29Merge pull request #3 from azul/feature/ignore_design_doc_changesjessib
ignore design document changes - do not trigger callbacks then
2013-11-28rescue from 404 when destroying dbAzul
Also logging per user db creation and destruction if they happen.
2013-11-28make sequence accept all kinds of jsonAzul
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-27ignore design document changes - do not trigger callbacks thenAzul
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-21Update default.yaml - couchdb security has members, not readersazul
2013-11-18Merge pull request #2 from azul/feature/delete-user-databasesjessib
Delete per user databases if the user has been deleted
2013-11-18use our logger - not just putsAzul
2013-11-18delete user db's on user deletion.Azul
2013-11-18fix issues with storing and retrieving the sequenceAzul
.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-18add a hook for reacting on user deletion.Azul
2013-09-30Merge pull request #1 from azul/feature/loggingjessib
log to file or syslog instead of STDOUT
2013-09-27clarify comment for log_file config settingAzul
2013-09-25log to file or syslog instead of STDOUTAzul
2013-09-16point to default config file for optionsAzul
add some explainations
2013-09-16Update Readme.md - we're not using http_stream from yajl anymoreazul
yajl/http_stream has been deprecated. We replaced it with the CouchRest::Database#changes
2013-09-16refactor - separate reading the last sequence from initializeAzul
2013-09-12use CouchRest::Database#changes, store and retrieve seqAzul
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-11use password and username from the config fileAzul
2013-09-11write _security to fresh couchAzul
2013-09-11create couch dbs as users are createdAzul
2013-09-10use our own JsonStream and a created callback in CouchChangesAzul
2013-09-10bringing over couch_changes from leap_ca including testsAzul
2013-09-10we do not need couchrest_modelAzul
2013-09-10fixup: tapicero.gemspec - not leap_ca.gemspecAzul
2013-09-10config file addedAzul
2013-09-10copying over skeleton from leap_ca which worked similarlyAzul
2013-09-10initial readmeAzul