Selfhosted

40394 readers

620 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:

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!

founded 2 years ago

MODERATORS

Revamped install for Piped (github.com)

submitted 1 year ago by Anarch157a to c/selfhosted

5 comments fedilink hide all child comments

Due to difficulties I had installing Piped, an alternative frontend for Youtube, I decided to improve and document the process in a better way. In the end, I pretty much redid the whole thing, leaving almost no stone un-turned. You can test my installer from my repo and post any comments and doubts here.

you are viewing a single comment's thread
view the rest of the comments

[–] lambchop 2 points 1 year ago* (last edited 1 year ago) (1 children)

I tried running both invidious and piped in docker behind an existing nginx. Invidious was so easy, 1 and done. My main issue with piped was piped running its own nginx, and it just returning a unconfigured landing page. After battling it I got the front end working by bypassing their nginx but it wouldn't talk to my piped back end, as soon as I pointed the front end at a public backend the option to point to mine disappeared. I'll try this installer and see how it goes.

[–] Anarch157a 0 points 1 year ago

You can run with your own reverse proxy Nginx if:

You expose the port used by the backend/API with a "ports:" setting on the compose file
Expose the socket used by the ytproxy container using a volume that points to a directory in the host

You'll still need 3 DNS names and a SSL certificate to cover all three.

TO configure your Nginx, you can use the template I provided on the config/ directory as a base.