javascript-sdk-design VS Teedy

- Process pitfalls: what choices might run afoul of big companies' security processes, or create unforseen challenges in getting the integration approved outside of the code-world.

The closest article I've found is https://sdk-design.js.org/ which has some great information at the beginning and end, but is somewhat generic in the middle. I suspect theres some great info buried in one-off technical blog posts at SaaS startups as well.

Theres also the option of learning from good examples - the obvious choice here being Stripe who are known for their great documentation & SDK design https://stripe.com/docs/development

Has anyone else found themselves in this position? How did you learn and improve (without having to do it the hard way of pushing bugs to your customers production sites!)? Did you find, or create, any useful resources on building modern browser SDKs?

I don't know about their features but apart from Mayan and Paperless-NG there are also Docspell, Papermerge, Iodestone, Hermes and Teedy.

An option may be to use https://github.com/sismics/docs and enable S3 support using https://github.com/s3ql/s3ql

Teedy is pretty good, what I use - https://teedy.io/

Hi all! I am trying to replace Evernote with something self hosted. Teedy looks ample so I’ve decided to give it a try but I am running‍ into issues. I am flowing the instructions here and I can get it installed but when I try to login for the first time, I always get an invalid user/password error... I’ve tried both options internal DB and SQL. I am using Docker on Synology using the built-in UI. Anyone else with this issue or clever ideas to troubleshoot it?

- teedy seemed promising, but the automated folder importer is broken - https://github.com/sismics/docs/issues/583