Upgrade from 2.1.1 to 2.3.0 now PUTing an attachment hangs

FYI, the reason for wanting to downgrade is that after I upgraded from 2.1.1 to 2.3.0 if I do : curl -vX PUT http://127.0.0.1:5984/my_database/001/test.mp3 --data-binary @test.mp3 -H "ContentType:audio/mp3" the upload hangs. This is on a 2.3.0 cluster with 2 nodes, previously on 2.1.1 it worked

Re: replicated blog engine?

Thanks! On 2/4/19 4:53 PM, Bill Stephenson wrote: PouchDB evolved very quickly in the past few years, so it’s worth another look. It seems to have stalled at the 7.0 version for close to the past year, but it’s a solid toolset with a nice API to interact with CouchDB. Running PouchDB in

Re: replicated blog engine?

PouchDB evolved very quickly in the past few years, so it’s worth another look. It seems to have stalled at the 7.0 version for close to the past year, but it’s a solid toolset with a nice API to interact with CouchDB. Running PouchDB in Node.js provides that same API on the server side to

Re: replicated blog engine?

Well, ok - but last time I looked (admittedly a while), PouchDB was basically intended to be a CouchDB equivalent that would run on a device that wouldn't support a full-blown CouchDB installation (e.g., a smartphone). I still like the old CouchAPP model - singlepage apps that could be

Re: replicated blog engine?

Look into the PouchDB API: https://pouchdb.com/api.html#replication And check into the CouchDB docs on replication. These are made to work together. You can probably trigger a replication a number of ways. As far as I know though, it’s not uncommon to use PouchDB on a server to manage CouchDBs

Re: replicated blog engine?

Now that just seems silly.  If CouchDB is already running, who needs Pouch? On 2/4/19 4:12 PM, Bill Stephenson wrote: You can run PouchDB on the server side in Node.js. An instance of that could be configured to live sync remote CouchDBs Kindest Regards, Bill Stephenson Tech Support

Re: replicated blog engine?

You can run PouchDB on the server side in Node.js. An instance of that could be configured to live sync remote CouchDBs Kindest Regards, Bill Stephenson Tech Support www.cherrypc.com 1-417-546-8390 > On Feb 4, 2019, at 3:10 PM, Miles Fidelman wrote: > > I'm

Re: replicated blog engine?

Hmmm… I not sure that does what you’re asking for. Let me ponder that a bit. Off the top of my head, it seems to me you can schedule replications in Fauxton. I’m not sure it you can configure them to live sync though. You probably can configure that in the client side DB with PouchDB though.

Re: replicated blog engine?

I'm thinking more of sync across multiple CouchDB back-ends.  I'm really not looking for a solution that runs completely in a browser, without installing PouchDB. On 2/4/19 4:05 PM, Bill Stephenson wrote: Yes, using PouchDB on the client side you can configure the text.js (the “publisher

Re: replicated blog engine?

Yes, using PouchDB on the client side you can configure the text.js (the “publisher app) to “live sync” the changes on their local db to your CouchDB, which will then sync all the connected clients. When a user views a post with the blog app, the app grabs the post from the CouchDB, so they

Re: replicated blog engine?

And that will replicate to other couchdb instances hosting the page? Miles On 2/4/19 3:47 PM, Bill Stephenson wrote: Yes, viewer comments are added to the blog post doc with a perl script running on the server side. I’d be glad to send you the script. Kindest Regards, Bill Stephenson Tech

Re: replicated blog engine?

Yes, viewer comments are added to the blog post doc with a perl script running on the server side. I’d be glad to send you the script. Kindest Regards, Bill Stephenson Tech Support www.cherrypc.com 1-417-546-8390 > On Feb 4, 2019, at 2:41 PM, Miles Fidelman

Re: Can a couched 2.3.0 be downgraded to 2.1.1 without changes to the data

Ah, we need to do a better job documenting this for sure. I think you _cannot_ do an in-place downgrade because the on-disk header format changed to v7 to include some metadata needed for the purge feature that was re-introduced in 2.3.0: https://github.com/apache/couchdb/commit/78a388d

Re: replicated blog engine?

Martin & Bill - thanks for your replies & pointers!  Both look interesting. Bill - a follow-up:  Does the single page blog, at azartiz.com, support replication of comments?  My goal is to publish a blog, distribute it to various social media sites, and build a single discussion community

Re: Can a couched 2.3.0 be downgraded to 2.1.1 without changes to the data

Have you tried replicating your data to the 2.2.1 DB? Bill > On Feb 4, 2019, at 2:19 PM, Compu Net wrote: > > Can a couched 2.3.0 be downgraded to 2.1.1 without changes to the data ?

Can a couched 2.3.0 be downgraded to 2.1.1 without changes to the data

Can a couched 2.3.0 be downgraded to 2.1.1 without changes to the data ?

Re: replicated blog engine?

Hi Miles, Build with PouchDB and CouchDB for offline first is my Blog example https://github.com/broerse/ember-cli-blog https://bloggr.exmer.com The program is also hosted in the CouchDB database. See https://github.com/martinic/ember-cli-deploy-couchdb I hope you like it. - Martin On Mon,

Re: replicated blog engine?

I’m not sure if it qualifies, but you’re welcome to take a look the blog I've made at azartiz.com. Kindest Regards, Bill Stephenson > On Feb 4, 2019, at 12:20 PM, Miles Fidelman > wrote: > > Hi Folks, > > I wonder if anybody has built a replicated blog engine on top of CouchDB - >

replicated blog engine?

Hi Folks, I wonder if anybody has built a replicated blog engine on top of CouchDB - something like WordPress that can run as multiple, synchronized, local copies. Anybody know of such a beast? Thanks very much, Miles Fidelman -- In theory, there is no difference between theory and