• 2 Posts
  • 12 Comments
Joined 1 year ago
cake
Cake day: June 3rd, 2023

help-circle

  • Lodion@lemmy.clickOPtoLemmy@lemmy.mlInstance relocation
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    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 :)





  • 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.








  • 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.