I didn't even know you could selfhost Streamio.
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: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
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!
Fair enough
I managed to selfhost the web interface, but I encountered an issue that I don't think I can fix...
I used this docker run command (not compose yet, just testing)
docker run -it --rm --name stremio-web -p 8080:8080 node:alpine sh -c """ apk add git git clone https://github.com/stremio/stremio-web --depth 1 cd stremio-web npm install npm run build npm install -g http-server http-server build/ -p 8080 -d false """
And I can reach the web ui. Now I can go into the settings page and set the backend url, which works perfectly. But when I go to the discover page nothing loads because it wants to reach stremio's own servers.
Note: To access my selfhosted services I use a firefox profile that doesn't have access to the internet, to be able to fully seflhost my stuff, that's why the connection to their servers is blocked.
Is there a way to proxy these remote connections from the backend or am I just lost at this point?