I didn’t, I spun up an entirely new instance.

Nah, part of the playbook sets up the initial Lets Encrypt certificate… so DNS needs to point to the new VPS. And the hostname needs to match the existing instance as it is referenced in the database.

Doesn’t matter now anyway, I went a different route :)

Thats what the “docker-compose down” is for in the second step :)

I’ve only reached level 23, but have been thoroughly enjoying it so far. Usually end-game is the real test, but by most reports finishing the campaign is ~40 hours of gameplay alone. Given the hundreds of hours I sank into D3 it was an easy buy for me.

edit: also the in game shop is totally ignoreable. Currently it isn’t shoved down your throat, you have to go looking for it. Given it is 100% cosmetics, I’m not fussed by it.

I’ve found email verification is finnicky to say the least. The Lemmy UI has some issues with users being stuck with spinning icons at various points for a start.

In the back end… email is a pain. If you’re using a public cloud VM and using the Lemmy provided docker/ansible postfix image, your users are unlikely to receive the verification emails as your server’s IP address is likely n a DNSBL somewhere.

If you use a third party SMTP service you may have more luck… but even then you’ll likely have issues.

I’ve disable email verification for these reasons, and rely on the answer to the signup question to vet applicants.

This seems to have more specifics.

As others have said, Jerboa is for android… I’ve heard mention of “mlem” for IOS, but have not seen it myself.

Sure, its a bit wordy… lacking in images with step by step instructions. If I had time I’d put something together with screenshots and figure out git and submit a pull request… maybe eventually.

Currently you have to start over.

Is there a newbie guide written up already somewhere? This is exactly the sort of things it needs, which should be linked to new signups.

Are there any published guidelines on the server requirements for an instance? I have my own instance running, seems to be working fine. But I’m reluctant to open it publically without an idea of if I’m setting myself up for failure or not.

Related, is there a way to entirely disable image uploads to my instance? I’m ok with it being a “reader” instance, but don’t want to be hosting content directly.