summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2014-11-10bugfix: pid file was not created correctly on startup. closes #6338HEADmasterelijah
2014-09-24updated Gemfile.lockelijah
2014-09-23Don't die when couchdb gets restarted (closes #6065)elijah
2014-09-09Merge pull request #21 from azul/bugfix/6047-invalid-sequence-on-bigcouchazul
new couchrest_changes deals with invalid sequence
2014-09-05new couchrest_changes deals with invalid sequenceAzul
It will also catch them on a bigcouch node and recover by reprocessing all changes.
2014-07-03Merge pull request #18 from azul/feature/recover-from-invalid-seqazul
Recover from invalid sequence file
2014-07-02Merge pull request #17 from azul/feature/catch-first-changeazul
Work around a bug in couchrest to catch the first change
2014-07-02Fix 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-02require couchrest_changes ~> 0.1.0 (fixes #4899)Azul
2014-07-02minor: rename TapiceroTest to ActionsTestAzul
that's what it actually tests
2014-07-01check for ARGV.first before testing itAzul
Otherwise we will crash if no args are passed. Now we print the usage message
2014-07-01pid issue remains to be solved - revert to sth workingAzul
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-01Merge pull request #16 from azul/feature/replicationazul
minor replication fixes
2014-06-27minor: lot's of small fixes to make replication workAzul
2014-06-27check for ARGV.first before testing itAzul
Otherwise we will crash if no args are passed. Now we print the usage message
2014-06-26Merge pull request #15 from azul/feature/replicationazul
initial take on replication
2014-06-26minor: include username in save_urlAzul
2014-06-23initial take on replicationAzul
2014-06-23update Gemfile.lockAzul
2014-06-06Merge pull request #14 from andrejb/feature/5517_update-soledad-design-docsazul
Update design docs for soledad splitted sync (#5517).
2014-06-05Update design docs for soledad splitted sync (#5517).db
2014-04-08Merge pull request #13 from andrejb/feature/5315_update-soledad-design-documentsazul
Update Soledad design documents.
2014-04-07Update Soledad design documents.db
2014-03-11Merge pull request #12 from azul/logging/merge-lines-for-nagiosElijah Sparrow
make warnings more readable to nagios - #5247
2014-03-11make warnings more readable to nagios - #5247Azul
2014-02-04Merge pull request #11 from azul/feature/gitignore-untrackedjessib
gitignore: vendor, .bundle and vim temporary files
2014-02-04Merge pull request #10 from azul/refactor/user-databasejessib
Refactor/user database
2014-02-04Merge pull request #9 from azul/test/integration-with-travisjessib
Test/integration with travis
2014-02-04Version 0.4.00.4.0Azul
minor changes improving stability
2014-02-04gitignore: vendor, .bundle and vim temporary filesAzul
2014-02-04prevent 409s and 412 and reraise them in testsAzul
Including tests that ensure this
2014-02-04refactor: moved prepare and destroy into user_event_handlerAzul
2014-02-04refactor: separate user event handlerAzul
2014-02-04refactor: init user_database with a couchrest dbAzul
2014-02-04test user deletionAzul
2014-02-04include sleep in the create_user part of the testsAzul
the changes feed and tapicero take some time to process the new user. Let's prevent timing issues by sleeping a second.
2014-02-04separate test setup test from actual testAzul
2014-02-04fix testsAzul
2014-02-04set db name correctly in tests and test itAzul
2014-02-04unify naming scheme - tapicero_test prefixAzul
2014-02-04hand config files on the command line to the daemonAzul
2014-02-04only set flags if they are definedAzul
2014-02-04first interesting testsAzul
2014-02-04add dummy integration testAzul
2014-02-04try to get require rubygems to work on travisAzul
2014-02-04updated Gemfile.lockAzul
2014-02-04initial test for running tapicero on travis ciAzul
2014-01-14properly refer to logger in user_databaseAzul
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