view the rest of the comments
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!
CasaOS is like a frontend for Docker, it has an "app store" where it's just a handful of clicks to install something.
Anyway, I did see that guide but the steps for Docker just say "Refer to Seerr Docker Documentation" which is well, kind of complicated.
I do have Portainer and know my way around it's basics if it makes it easier.
If you have portainer, it should be relatively easy.
First make a backup of the old config folder (I just copied mine to a new seerr folder) then you insert your current data into the docker compose-file they show at your link and import that as a stack. Boom, done.
If you have an existing stack with, let's say, radarr and sonarr and plesk and overseerr, then you can backup the old compose file, and replace only the overseer part with the code from the given compose config.
ok great thank you!