- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
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 must log in or register to comment.
What is piped?
Privacy conscious Interface for Youtube, with a much cleaner and faster interface. You can try a public instance from this list: https://github.com/TeamPiped/Piped/wiki/Instances
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.
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.
How would this work with a pre-existing reverse proxy?
