Administrator of thelemmy.club

Nerd, truck driver, and kinda creeped that you’re reading this.

  • 2 Posts
  • 57 Comments
Joined 1 year ago
cake
Cake day: June 14th, 2023

help-circle








  • Use Cloudflare or PorkBun.com for cheap, no bullshit domains. As for the email host, self hosting not recommended. It’s a long battle to be not blocked by every other provider.

    I recommend purelymail.com - no cost to add (even multiple!) custom domains, unlimited users, only pay for mail usage and storage. Go for advanced pricing until it starts costing you more than $10/yr. (Which it shouldn’t if it’s just you. Seriously this thing is cheap!) I just passed my one year anniversary with PurelyMail, and have spent $6 so far. This is my most expensive month, 85¢. And that’s only because I host a public Lemmy instance (small) and we had a few hundred spam signups which sends an email each time.

    This will give you a total yearly price WAY under what Google or Microsoft will give you. Google is like, $7.20/user/month.

    And if for some reason that service goes down one day, as long as you still have a mail client with your email stored in it you should be able to just switch providers and import your emails from your client. Make some backups.



  • It’s undergoing massive development, it basically went from nothing to nearly full featured in two years.

    The breaking change just means you need to actually do something before updating. The software isn’t quite ready to be put on auto-update yet. Honestly the way the devs aren’t afraid to break things I think has contributed to the fast development.

    Just be sure to keep a secondary backup of your photos which you should do either way.






  • Most containers don’t package DB servers, Precisely so you don’t have to run 10 different database servers. You can have one Postgres container or whatever. And if it’s a shitty container that DOES package the db, you can always make your own container.

    that those images are configured according to your actual end-users needs, and not to some packager’s conception of a “typical user”: do you do mailing? A/V calling? collaborative document editing? … Your container probably includes (and runs) those things, and more, whether you want it or not

    that those images are properly tuned for your hardware, by somehow betting on the packager to know in advance (and for every deployment) about your usable memory, storage layout, available cores/threads, baseline load and service prioritization

    You can typically configure the software in a docker container just as much as you could if you installed it on your host OS… what are you on about? They’re not locked up little boxes. You can edit the config files, environment variables, whatever you want.