This. Docker compose down, schlep the data over, update paths and permissions, docker compose up. Done.
Probably bring it up one step at a time so you can more easily identify anything you missed.
Comment on Please weigh in: Transfer of Docker stacks to Debian
Botzo@lemmy.world 3 days ago
rsync
Built-in, picks up where it left off if you accidentally cancel it by running the same command again, and dead simple.
Permissions for the files will probably be a little broken moving to Linux, but chmod is also easy to use and can work at the directory level.
frongt@lemmy.zip 3 days ago
Botzo@lemmy.world 3 days ago
If you need to change the references in the compose or env files:
- use sed to replace text in .env
- use variables and interpolation in compose
lambalicious@lemmy.sdf.org 3 days ago
Be wary when you use rsync, to not upgrade past version 3.4.1. Later versions were vibecoded / slopecoded and cause data loss.
confusedpuppy@lemmy.dbzer0.com 3 days ago
I too was upset with the use of Claude/AI/LLM’s in the rsync project. The maintainer received a lot of public backlash and as a result people have offered their time to help the maintainer with this project.
Since the backlash, the use of agents has been drastically reduced. That seems like a very human and overall positive response. It sucks that it happened. It’s nice that people are now doing the work again. The response could have been a lot worse. I can be forgiving in this specific situation.
lambalicious@lemmy.sdf.org 3 days ago
Oh! I might check up how the repo is doing during the weekend, might merit an upgrade once the next major (3.5 if I’m getting my numbers right) comes around.
frongt@lemmy.zip 3 days ago
Fuck’s sake. What was the actual bug introduced? I skimmed the issues on GitHub and nothing jumped out at me.
lambalicious@lemmy.sdf.org 3 days ago
I don’t remember the exact bug but just search for “data loss” and/or “changed behaviour”, either it wil come up or the devs have been whitewashing their inclusion of AI and censoring discussions.
frongt@lemmy.zip 2 days ago
I don’t see it, but I do see plenty of criticism of the use of claude.
I searched issues for “compare-dest”, which seems to be the part they were complaining about being broken, and I didn’t see any issues that looked relevant. I also looked through the commit log between 3.4.1 and 3.4.3 for anything mentioning that option and didn’t see anything there either. So right now it just looks like fearmongering to me.
Botzo@lemmy.world 3 days ago
Dammit.
lambalicious@lemmy.sdf.org 3 days ago
Don’t sweat it (yet) and just lock it in your package manager. If you are on Debian, the last reasonable versions can be apt get from snapshots.debian.org and then just apt pin / apt mark hold those.
moonpiedumplings@programming.dev 3 days ago
Debian has a policy of only cherry picking security updates, or critical bugfixes, in order to ensure maximum system stability. In general, they don’t do entire program updates or additional features. For the 4 year lifecycle of a Debian release, it will behave the same as it did yesterday.
As of today, current version of rsync in Debian’s stable’s packages is 3.4.1: packages.debian.org/stable/rsync (archive).
The versions with significant LLM assistance are 3.4.3 and later.