@nyanide I thought about trying to run two of them behind an nginx proxy. I think I could just set the web.endpoint to another port number on the second instance, yeah?
@prettygood There's also Postgres taking up too much storage space if you start to run more than 1 Pleroma instance at once. FRE literally sat doing basically nothing for months and DB dump was 7 gigs, Pleroma is a hungry girlie.
@nyanide@prettygood I've seen beam get hungry for memory for no reason, oom and be fine for weeks again multiple times. It went from maybe a gigabyte of allocated memory to 4x of that in a minute.
I don't think it likes running with other applications on the same host like with the process spin trick it uses to convince the kernel scheduler to not pause the process and give the resources to something else. There might be some obscure argument for it, but who the fuck knows those.
@phnt@nyanide in my experience the only problem I've had has been epmd not exiting gracefully and needing to be killed manually. I suspect this is because both pleroma and ejabberd are using it so when one service stops it doesn't accept the sighup or whatever because the other thing is using it. So I just added "pkill epmd" to my scripts :-p
@prettygood@nyanide epmd is supposed to be started as a separate service since it is supposed to be a nameserver for other Erlang nodes on the network, but very few people do that. I think only Debian has a service file for it.
@nyanide this is why my vaporware runs an infinite amount of domains at the moment, wonder how much hassle a multi-tenant pleroma would be, a lot of it sucks because you'd still be duplicating most of the data among prefixes