Age | Commit message (Collapse) | Author | |
---|---|---|---|
2014-07-03 | Merge pull request #18 from azul/feature/recover-from-invalid-seq | azul | |
Recover from invalid sequence file | |||
2014-07-02 | Merge pull request #17 from azul/feature/catch-first-change | azul | |
Work around a bug in couchrest to catch the first change | |||
2014-07-02 | Fix couchrest missing the first change (#5452) | Azul | |
CouchRest::Streamer will ignore the first line from a stream. Normally that's the line opening the results array. But for continuous feeds couch will start streaming the array elements right away. So we miss the first one. There's a pull request pending for couchrest here: https://github.com/couchrest/couchrest/pull/104 Until it's merged we'll monkeypatch. Also stopping tapicero again after travis run. | |||
2014-07-02 | require couchrest_changes ~> 0.1.0 (fixes #4899) | Azul | |
2014-07-02 | minor: rename TapiceroTest to ActionsTest | Azul | |
that's what it actually tests | |||
2014-07-01 | check for ARGV.first before testing it | Azul | |
Otherwise we will crash if no args are passed. Now we print the usage message | |||
2014-07-01 | pid issue remains to be solved - revert to sth working | Azul | |
We've seen two instances of tapicero running on the production servers. The reason is that we are using two different places for the pid file - one for root and one for a normal user. In this scenario tapicero started by root will not notice the tapicero run as a normal user and vice versa. One idea was to solve this by always using /var/run/pid. However this also requires write privileges to that place which essentially only root has. So let's keep the two different places and just make sure we ALWAYS run tapicero as the same user. | |||
2014-07-01 | Merge pull request #16 from azul/feature/replication | azul | |
minor replication fixes | |||
2014-06-27 | minor: lot's of small fixes to make replication work | Azul | |
2014-06-27 | check for ARGV.first before testing it | Azul | |
Otherwise we will crash if no args are passed. Now we print the usage message | |||
2014-06-26 | Merge pull request #15 from azul/feature/replication | azul | |
initial take on replication | |||
2014-06-26 | minor: include username in save_url | Azul | |
2014-06-23 | initial take on replication | Azul | |
2014-06-23 | update Gemfile.lock | Azul | |
2014-06-06 | Merge pull request #14 from andrejb/feature/5517_update-soledad-design-docs | azul | |
Update design docs for soledad splitted sync (#5517). | |||
2014-06-05 | Update design docs for soledad splitted sync (#5517). | db | |
2014-04-08 | Merge pull request #13 from andrejb/feature/5315_update-soledad-design-documents | azul | |
Update Soledad design documents. | |||
2014-04-07 | Update Soledad design documents. | db | |
2014-03-11 | Merge pull request #12 from azul/logging/merge-lines-for-nagios | Elijah Sparrow | |
make warnings more readable to nagios - #5247 | |||
2014-03-11 | make warnings more readable to nagios - #5247 | Azul | |
2014-02-04 | Merge pull request #11 from azul/feature/gitignore-untracked | jessib | |
gitignore: vendor, .bundle and vim temporary files | |||
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 | gitignore: vendor, .bundle and vim temporary files | Azul | |
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 | |