Comment on Mixarr – a music discovery companion for Lidarr/Plex

priapus@piefed.social ⁨4⁩ ⁨days⁩ ago

• aquantumofdonuts@lemmy.world ⁨4⁩ ⁨days⁩ ago

  Hi, it might but I haven’t explored that. I’ll look into it. Would you want to roll your own SQLite, or just have that containerized instead of postgres?

  source

  • priapus@piefed.social ⁨3⁩ ⁨days⁩ ago

    SQLite doesnt require you to have any service running, the DB is just stored in a file which the program accesses through an SQLite library. I think its the best option for selfhosted software, as its very lightweight and more than performant enough for 99% of these use cases.

    source

    • curled@lemmy.dbzer0.com ⁨3⁩ ⁨days⁩ ago

      Performance isn’t the only advantage to a full postgres deployment. I have a central database for all of my self hosted apps which makes it really easy to back it all up.

      I’ve had a lot of problems in the past from software crashes that left sqlite files in a corrupt state, backups where the sqlite file wasn’t properly closed leaving it in a weird unlockable state, transactions not completing when swap is used, etc. Besides that sqlite really doesn’t play nice with NFS, which is the basis for quite a few cloud storage providers.

      “Best option” really depends on what self hosting looks like in your specific setup.

      source

      • priapus@piefed.social ⁨2⁩ ⁨days⁩ ago

        Yeah, I wasn’t trying to say SQLite is universally better. I shouldn’t have said best option, I really meant best default. I don’t think the majority of users are running a central db, most will just spin-up docker compose files for each service and end up with multiple SQL versions running.

        I’ve had a lot of problems in the past from software crashes that left sqlite files in a corrupt state

        I have had this issue, but it was always easily recoverable. I haven’t had the same issues with backups, although a lot of the software I use that’s running SQLite has a builtin backup feature, then I just backup that directory to a cloud service.

        Besides that SQLite really doesn’t play nice with NFS, which is the basis for quite a few cloud storage providers.
        Also a good point, I just don’t think the majority of users are using NFS for their DBs.

        When an app is using an ORM already, I think they might as well make sure it supports both SQLite and a hosted DB like Postgres

        source

        • -> View More Comments