I was doing that as well, but it wasn't the problem. The problem was apparently caused by a too-long site name
db0
joined 2 years ago
I managed to get it to run. I checked in postgresql logs and it seems it was caused by trying to add into site. Apparently the site name cannot be more than 20 chars but this is mentioned nowhere in the documentation.
And when this happens, it causes this cascade of somehow trying to recreate the admin again and again, which is a red herring after all.
Worse. Restarting the container, seems to keep recreating that user 3 times again. Then always fails with
lemmy_1 | Error: LemmyError { message: None, inner: value too long for type character varying(20), context: "SpanTrace" }
I dropped the contraints manually to test, and it indeed seems to create the admin account 3 times for some reason!
Even if you choose Hetzner, it won't even know it has anything to do with piracy because it will be just hosting the DB, and nobody will know where your DB is. That fear is overblown.
Likewise believe me a dedicated server is night and day from a VPS.
Do you have the frontend a DB serving in the same VPS? If so it would be a great time to split them. Likewise if you DB is running in a VPS, you're likely suffering from significant steal from the hypervisor so you would benefit from switching to a dedicated box. My API calls saw a speedup of 10x just from switching from a VPS DB to a Dedicated Box DB.
I just checked OVH VPS offers and they're shit! Even at 70 Eur dedicated on hetzner, you would gain more than double those resources without steal. I would recommend switching your DB ASAP for immediate massive gains.
If you're wondering why you should listen to me, I built and run https://aihorde.net and are handling about 5K concurrent connections currently.
I don't have something to compare it to. As it's still empty, performance is still good.