• 1 Post
  • 8 Comments
Joined 1 year ago
cake
Cake day: July 3rd, 2025

help-circle

  • 2nd DB would be on the NAS but its not being used by the app, so as long as it’s asynchronous writes, you should be okay

    But then I have to maintain it too. And it will be using RAM that was supposed to only be for servicing RAID. On a platform where RAM can’t grow

    For sure my setup will be growing and changing with time. But ATM this “prod” db lives only on laptop’s SSD


  • replication in the database it self

    AFAIK db replication would require running another db on NAS. Which I tried to avoid

    I have another cronjob that takes a backup into the first database docker init folder. Older backups end with -date so they won’t get picked up by the init script. You can do similar with just docker.

    Yeah, that’s why I’m thinking to do. Have a container that watches changes to db data and rsyncs those into the NAS for safekeeping. My main goal in all of this is so db data won’t die with laptop’s SSD


  • You can easily just try it out though

    Yeah, but if that setup leads to problem in a few months, I won’t catch that. That’s why I decided to ask and judging by the other answer, I dodged a bullet here

    Now I’m thinking of setting up something like this. Maybe even in another container? One volume with data bound, one with NFS and a bunch of scripts in entrypoint to rsync(?) between the two on inotifywait. There is lsyncd but it’s been unmaintained for two years now