library VS mayan-edms

This reminds me a lot of the NY Times' Library project: https://github.com/nytimes/library. You use an editing environment that people are familiar with (google docs), and you build organizational and workflow stuff around it. Library rendered the document content itself with a link to edit (favoring the reader use case), whereas Hermes embeds the google docs UI.

The lack of code blocks in google docs makes it tough for a centralized document repository for an engineering org. For companies using Quip it could work really well...except that I don't think quip lets you embed the editor like that.

Everything that's been built so far for Hermes looks cool. My personal opinion is that it'll need more UX iteration for it to really take off.

Try Library instead of Confluence, if you're using the Google Suite.

This is pretty awesome! If anyone wants something similar but for documentation check this out: https://github.com/nytimes/library

Mayan EDMS / Mayan EDMS · GitLab

I always love open-source projects for their quality and the amazing community who build it through their contributions. Whenever I'm in need of any professional software for day-to-day productivity or hobby projects for personal use, I always search in google along with "open-source" keyword. I found so many such open-source projects which I end up using very frequently. apps.diagrams.net (formerly draw.io), Greenshot, Mayan EDMS, WinMerge, Notepad++, Visual Studio Code are to name a few.

I'm trying to run Mayan EDMS in a docker container and I'm using the official docker compose from here: https://gitlab.com/mayan-edms/mayan-edms/-/blob/master/docker/docker-compose.yml

As far as actual solutions to my original question...looks like Mayan actually does support transparent encryption for storage and transport starting with version 3.4 (and mentioned here) but it's virtually undocumented as far as I can tell.