8
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 18 Jun 2023
8 points (100.0% liked)
Self Hosted - Self-hosting your services.
11399 readers
2 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules
- No harassment
- crossposts from c/Open Source & c/docker & related may be allowed, depending on context
- Video Promoting is allowed if is within the topic.
- No spamming.
- Stay friendly.
- Follow the lemmy.ml instance rules.
- Tag your post. (Read under)
Important
Beginning of January 1st 2024 this rule WILL be enforced. Posts that are not tagged will be warned and if not fixed within 24h then removed!
- Lemmy doesn't have tags yet, so mark it with [Question], [Help], [Project], [Other], [Promoting] or other you may think is appropriate.
Cross-posting
- !everything_git@lemmy.ml is allowed!
- !docker@lemmy.ml is allowed!
- !portainer@lemmy.ml is allowed!
- !fediverse@lemmy.ml is allowed if topic has to do with selfhosting.
- !selfhosted@lemmy.ml is allowed!
If you see a rule-breaker please DM the mods!
founded 3 years ago
MODERATORS
I unretired an old racknerd vps and got it running on there.. works great!
Just need to now figure out how to move it to something that can actually cope with it lol..
Any ideas how to backup an instance and move it?
I guess it would be a matter of getting a new VPS, pointing my domain to it, reinstalling and then moving over the .live folder?
Yes, you will want to copy the entirety of the
Lemmy-Easy-Deployfolder recursively, including thelivefolder.However, all important data is also stored in Docker volumes on the system. There isn't a great way to migrate Docker volumes between systems, but there are a few options. One I have not personally used, but seems to look good, is
vackup:https://github.com/BretFisher/docker-vackup
You'll want to run
docker volume lson your current system, and make sure that when you migrate them to the new system, all the volume names are exactly the same. Then, if you rundeploy.sh -f, it should pick everything up and deploy.Do note: if Docker Compose itself does not create the volume with the right tags, it will still work, but it will print some warnings to the console. Here is an issue discussing it and some potential hacks you can use to add the right tags:
https://github.com/docker/compose/issues/10087
Finally, if you need to re-create a volume on the new system with tags like the above issue mentions, you can try migrating data over between named volumes on the same system using this helpful oneliner (don't forget to change the volume names in all the places in this command):
https://www.commands.dev/workflows/rename_docker_volume
In short, it's a bit hacky, but it can be done.
Good luck!