“🚀 Easy to install, scalable and secure alternative to Notion, Outline or Confluence”

This! This is how you do it! Public money, invested in initiatives to remove dependence on outside actors by creating open source products with great engineering.

“While Docs is a public driven initiative our licence choice is an invitation for private sector actors to use, sell and contribute to the project.”

Today is a day where I'm proud to be European!

https://github.com/suitenumerique/docs

GitHub - suitenumerique/docs: A collaborative note taking, wiki and documentation platform that scales. Built with Django and React.

A collaborative note taking, wiki and documentation platform that scales. Built with Django and React. - suitenumerique/docs

GitHub
@shezi but why does it have a full-blown k8s as prerequisite? 😞
@bison

@ttk @shezi @bison

does it? at least here is a docker-compose file:

https://github.com/suitenumerique/docs/blob/main/docker-compose.yml

remove the dev dependencies and it looks like a standard django celery deployment to me.

sure, installation.md is an example for how install it on k8s but there is no hard requirement for this.

docs/docker-compose.yml at main · suitenumerique/docs

A collaborative note taking, wiki and documentation platform that scales. Built with Django and React. Opensource alternative to Notion or Outline. - suitenumerique/docs

GitHub

@ttk @shezi @bison What I dont understand is why they made OIDC a hard requirement.

From a user POV thats bullshit, django already has a full blown authn and authz system built-in. Requiring a 3rd party OIDC provider just raises the bar for simple deployments and hinders adoption.

@xchange @ttk @bison

I assume that's because the project is still “paying-customer-first”. If you look at their demo environment, that's integrated with the french government auth suite, so naturally they'd integrate with that.

In any case, it shouldn't be too hard to either modularise that or add an oidc provider into the compose files. In fact, the k8s documentation even contains a keycloak for exactly that purpose.

@shezi @ttk @bison of course it should not be a problem, but now you have keycloack and just another moving part that you have to take care of. which is fine for larger orgs but adds unnecessary overhead for smaller installs.

@xchange @bison

collab on adding regular user auth? or maybe add allauth and have optional social auth?

@shezi @bison might be a viable path forward, depending on how project governance was setup
docs/src/backend/core/authentication/backends.py at eb23aefd55ecb3eb1b6acfbac5d10ecfe5e4bb84 · suitenumerique/docs

A collaborative note taking, wiki and documentation platform that scales. Built with Django and React. Opensource alternative to Notion or Outline. - suitenumerique/docs

GitHub

@xchange @bison

as far as I can see, model authentication is also enabled, and they even have a custom user model. Shouldn't be too hard to. expose that as main auth mechanism, or add other mechanisms. I'll have to play around with that a bit.