[kastden]

This looks very nice! It’s not mentioned in the README, so I’m wondering how persistence is handled? EDIT: To be clear, I see backups is mentioned, but I’m wondering if it’s a database file like sqlite3 or something else.

[sissbruecker]

Yes, currently it uses a SQLite3 DB for storage. The DB is created or updated with Djangos migrate command which runs when the Docker container starts. The DB file can be found in the data folder.

Thanks for your comment, it made me realize I stopped thinking about persistence at some point and now I had to look up on SQLite usage in production. However for the apps current use-case of handling one account / one person it seems fine to use SQLite.

[kastden]

Thanks for the explanation! I think SQLite is fine for this too.

My use case would be running this on AWS ECS, but since this wouldn't get written to very often (probably) and the file hopefully wouldn't be very big either, I could just have the container or a sidecar pull it from S3 on startup and sync it at regular intervals and on shutdown.

[catalogia]

SQLite is a great choice for a project like this. Particularly for a project like this, dealing with something as intimate as bookmarks, it's nice to not have to worry about how I'd get my data out of it should I ever decide to stop using the software. That provides some nice peace of mind.

Incidentally Firefox also uses SQLite for storing bookmarks (among other things.)