I’ve got copyparty working behind a proper reverse proxy. This allows it to be publicly accessed using a nice domain name with SSL.
A reverse proxy (on a cloud VPS) re-directs the https traffic into my home lab where Copyparty is running on a Raspberry Pi 4:
Some geek friends of mine did some stress testing all at once on this Copyparty server. It could take a savage, nasty beating and survive.
Dear fellow or potential fellow gotosocial instance admins,
I’ve come up with a novel way to set up a gotosocial server behind a reverse proxy, which avoids the use of making new firewalling rules - both on a VPS, and creating port forwarding on one’s home router. This method is ideal for minimizing the cost of running one’s own ActivityPub/Mastodon server, in a way that leverages inexpensive fast storage on the backend (say, on a RaspberryPi 5, 2GB of RAM, with an NVMe).