this post was submitted on 22 Jul 2023
4 points (75.0% liked)

Selfhosted

40006 readers
622 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

Hi! I need some help please, I can't seem to be able to figure this out myself.


Stremio: The Next Generation Media Center

They have a docker container with the backend, and they also have the web frontend Dockerfile.

I am running already the backend with docker, but if you go to the ip:port it will redirect to Stremio's own hosted frontend, that then uses your backend.

But I instead want to host both the frontend and backend, has someone already done this before? I couldn't find much and the Dockerfile is not of much help.

Thank you!

you are viewing a single comment's thread
view the rest of the comments
[–] SmallAlmond@lemmy.dbzer0.com 0 points 1 year ago* (last edited 1 year ago) (1 children)

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.

v3-cinemeta.strem.io GET

Is there a way to proxy these remote connections from the backend or am I just lost at this point?

[–] itmike@fikaverse.club 1 points 1 year ago (1 children)

@SmallAlmond I don't know much about streamio, but I noticed this on their webpage;

"There is also a Guest mode at signup, which requires no data whatsoever: in this mode, no calls are made to our backend. However, it comes at the expense of useful features, such as being able to sync your library across devices."

🤔

[–] SmallAlmond@lemmy.dbzer0.com 1 points 1 year ago

I mean... That's what the webui I deployed has, the "guest mode login", but it still makes those http requests to their servers :/