Im nott sure setting up a sidekiq queue on a remote server is a good idea honestly. Its ok if its on a different server in the local network if you have a nice fast network, but I wouldnt do it over the internet.... that said, you could do itt in theory, I just dont think it would perform very well (haven't tried though).
@freemo it would be a server on the same local network (it would also be on a private VLAN).
@KuJoe In that case it shouldnt be a problem and really shouldnt require any sort of special setup either.
@freemo I mainly don't know how to actually do it. Ruby/Sidekiq is new to me so I'm not sure what changes need to be made to what files to allow remote Sidekiq queues.
@Gargron described doing it here, but provides no guidance on how it's done: https://blog.joinmastodon.org/2017/04/scaling-mastodon/
@KuJoe You need to bind all services like Postgres, Redis, etc to your internal IP. Then you install Mastodon on the remote machine and start the sidekiq there. For the object store you can use Minio. Say goodbye to localhost.
@jan so how do I run the Sidekiq and Puma processes on other servers?
@KuJoe You need a second Mastdon installation on the remote server and all your services like Postgres, Redis, and file storage etc. needs to communicate over the internal IP. Then you start mastodon-sidekiq with systemctl on the remote instance.
@lucifargundam @freemo Thanks! I tagged the only 2 people I could think of so I appreciate you tagging another who might be able to help.