ufobat opened a new issue #346: _replicate vs _replication API endpoints URL: https://github.com/apache/couchdb-documentation/issues/346 I am currently writing a little script that helps me to setup a replication between two couchdbs. Therefore I want to read the current replication jobs, check if my desired job is already there. If not, I would setup a replication. If there are jobs that are no longer required (doesnt match my criteria) I wanted to remove the those. While doing so I was falling in some traps: In the [Replication Section](http://docs.couchdb.org/en/latest/replication/replicator.html#replicator-database) of the documentation there are `_replication` and `_replicate`. It took me a while to realize that those two are actually not the same names. First I send my "replication requests" into `_replicate` instead of `_replication`. It took several minutes before something showed up in `_schedule/jobs`. I was confused that there was no way to show my configuration immediatly. What is the expected behaviour when you configure a replication to `_replicate` and what is the expected behaviour when you write it to `_replication`? I would like to have some information in the documentation 1) that there are actually those two, and explain what is used for which usecase. (I dont know it, could you give me to write a PR, please) 2) that explains the expected behaviour in way like: When you do X you can see Y after Z happend. (Like When you write to `_replicate` it takes at least x seconds [x secons](http://docs.couchdb.org/en/latest/config/replicator.html#replicator/interval) and then you can find the results in `_schedule/jobs` - not sure if that is correct) If you could provide me some information I will gladly write a PR. :-)
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
