next-starter-blog VS LinkAce

I don't think it is as soupy as you say.

Flask is split up into a few Pallets projects - Flask, Werkzeug, Markupsafe, Click, itsdangerous, Jinja2 - but they're all from the same stable group. This split makes them more useful as independent libraries, rather than one big framework.

Ditto two more (Alembic and SQLAlchemy) are also from a very stable group. It would be nice if Alembic used Jinja2 instead of Mako, of course, but it's a dev-time dependency and so it's lower risk in my opinion.

I agree that at the thing Django does (forms + a SQL database) it does it with fewer dependencies than Flask. But that doesn't mean Flask has loads of dependencies; it has an appropriate number for the task you're doing. I was more comparing Flask to actual dependency soup ecosystems[0].

[0] https://github.com/rizkimcitra/next-starter-blog/blob/main/p...

I rarely use the built-in browser bookmarks. The important links to services and other things, I keep in a self-hosted service, Linkace. The problem is that I am trying to keep all my important information in a future-proof format, and that was the reason I migrated from Notion (and Evernote before) to Obsidian: the ability to save all data in plain text.

You might want to look at https://www.linkace.org

Some others I looked at: https://github.com/Kovah/LinkAce/ (PWA) https://github.com/sissbruecker/linkding https://github.com/ndom91/briefkasten (PWA) https://github.com/Daniel31x13/link-warden (PDF)

I found an official compose file from the project's GitHub page, which has some differences to yours.

Linkace for syncing bookmarks and Vaultwarden/Bitwarden for passwords and logins.

Linkace is a good option.