Authentication strategies?

[aral]

First off, thank you for authoring and sharing this – it sounds awesome.

I was just wondering how you’re handling authentication for the app(s) in which you’re using this (for the remote sync).

I realise we’re pulling vuex in a direction the Vue folks don’t necessarily want it to go (https://forum.vuejs.org/t/vuejs-vuex-data-synchronization-with-server-backend/16340/17) and so it’s not necessarily realistic to expect issues like authentication to be integrated but it is also a direction that makes perfect sense moving forward and looking towards a decentralised/p2p web. For an example of how a similar project (not offline-first) is handling it, see https://github.com/feathers-plus/feathers-vuex

Thanks again for your great work.

[maxmilton]

@aral we're deprecating this as we've decided to migrate our projects from vue to svelte. You're welcome to fork this or use any code if it's useful to you.

As for auth, we done it separately to @wearegenki/db. We had an API with a node server which would handle auth and send the user a cookie for the database. This cookie would get sent to our Couchbase sync gateway and allow for connections. Regular CouchDB also worked the same way.