Selfhosted
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:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
Thank you all for your input. ultimately I discovered that the volumes that had been stored inside docker's directory (on WSL) were actually not the ones I was worried about losing.
My container directory where my compose files are categorized and stored turned out to have everything I really needed. It did take reducing the hashed docker internal volumes to tar.gz to figure that out.
Anyway, I just stopped (not "down") docker and copied the directory onto one of my extra SSDs. Then I shut down the host, took out the Windows nvme, booted from my Debian SSD, made and mounted a new master container directory, and copied the files over. I had to update the compose and config files to use the new file paths, but once that was done, I did a compose up and everything took off pretty much without a hitch.