4 ms·
There're two instances at the moment: https://github.com/TeamPiped/Piped/wiki/Instances https://github.com/TeamPiped/Piped/wiki/Instances Here's the documentat
by emanuelpina 5y ago
There're two instances at the moment: https://github.com/TeamPiped/Piped/wiki/Instances https://github.com/TeamPiped/Piped/wiki/Instances
Here's the documentation, including how to self-host an instance: https://piped-docs.kavin.rocks/ https://piped-docs.kavin.rocks/
- denton-scratch 5y agoAh, Docker. Looks like you have to run a minimum of TWO servers (or containers). You need a Java 11 server, and at least one golang proxy. Looks like "self-hosting" means, in practice, cloud hosting.
- danielheath 5y agoI mean, two docker containers isn’t zero overhead but it’s a long way from “needs multiple boxes and you have to pay someone to manage it”. A systemd unit file to run a docker container isn’t a hard thing to write.
- denton-scratch 5y agoI don't use Docker or systemd. I don't need to rehearse my objections to systemd; I object to Docker because it's a proprietary skin wrapped around open-source container mechanisms. I run Xen VMs, and I don't want to dedicate two VMs to something like this (my VM host has 16GB of RAM). I'm not saying this solution is no good; it's just not a match for me.
- nargek 5y agoWhy would you have to dedicate two vm ? You can use containers (LXC) and that's it.
- denton-scratch 5y agoI could use LXC; I looked into it about 5 years ago, and it looked reasonable. But I can only administer a limited number of technology bundles, and I went with Xen for virtual hosting. If I deployed Piped as LXC, I'd have to figure out how to do it (LXC is not The Docker Way, and the installation instructions are for Docker). I don't mind admin work - I quite like it - but for me, it's pure overhead, since I run nothing else under LXC.
- maccolgan 5y agoTry Podman, I think you'll like it.