Age | Commit message (Collapse) | Author | |
---|---|---|---|
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 | test user deletion | Azul | |
2014-02-04 | include sleep in the create_user part of the tests | Azul | |
the changes feed and tapicero take some time to process the new user. Let's prevent timing issues by sleeping a second. | |||
2014-02-04 | separate test setup test from actual test | Azul | |
2014-02-04 | fix tests | Azul | |
2014-02-04 | set db name correctly in tests and test it | Azul | |
2014-02-04 | unify naming scheme - tapicero_test prefix | Azul | |
2014-02-04 | hand config files on the command line to the daemon | Azul | |
2014-02-04 | only set flags if they are defined | Azul | |
2014-02-04 | first interesting tests | Azul | |
2014-02-04 | add dummy integration test | Azul | |
2014-02-04 | try to get require rubygems to work on travis | Azul | |
2014-02-04 | updated Gemfile.lock | Azul | |
2014-02-04 | initial test for running tapicero on travis ci | Azul | |
2014-01-14 | properly refer to logger in user_database | Azul | |
2014-01-14 | fix UserDatabase#prepare | Azul | |
2014-01-13 | Merge pull request #8 from azul/bugfix/fix-for-revisions-starting-above-1 | jessib | |
Revisions sometimes start at 2 - work around this | |||
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 | ensure we log all errors | 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. | |||
2014-01-02 | hotfix: use working couchrest_changes version and yajl 1.1.0 | Azul | |
yajl 1.2.0 required mkmf on the server which currently is not present | |||
2014-01-02 | use latest couchrest_changes for more stability | Azul | |
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-22 | Merge pull request #6 from azul/deploy-design-docs | azul | |
Deploy design docs | |||
2013-12-22 | Merge pull request #5 from azul/feature/use-couchrest-changes | azul | |
Version 0.2.0: use CouchRest::Changes | |||
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-29 | Merge pull request #4 from azul/feature/more_robust_sequence_handling | jessib | |
Feature/more robust sequence handling | |||
2013-11-29 | Merge pull request #3 from azul/feature/ignore_design_doc_changes | jessib | |
ignore design document changes - do not trigger callbacks then | |||
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-21 | Update default.yaml - couchdb security has members, not readers | azul | |
2013-11-18 | Merge pull request #2 from azul/feature/delete-user-databases | jessib | |
Delete per user databases if the user has been deleted | |||
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-30 | Merge pull request #1 from azul/feature/logging | jessib | |
log to file or syslog instead of STDOUT | |||
2013-09-27 | clarify comment for log_file config setting | Azul | |
2013-09-25 | log to file or syslog instead of STDOUT | Azul | |