Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
@avguser@lemmy.world
I'll second not self hosting email unless you're in it for the experience.
I'd also strongly caution against hosting email for friends and family unless you want to own that relationship for the rest of your life.
If you do it anyway, you're going to end up locked into whatever solution you decide for a long time, because now you have users who rely on that solution.
If you still go forward, don't use Google (or msft). Use a dedicated email service. Having your personal domain tied to those services just further complicates the lock in.
(I did this over a decade ago, with Google, when it was just free vanity domain hosting. I've been trying for years to get my users migrated to Gmail accounts.)
If I had it all to do over again. I'd probably setup accounts as vanity forwards to a "real" account for people who wanted them. That's easy to maintain, move around, and you're not dealing with migrating peoples oauth to everything when you want to move or stop paying for it.
I have a bunch of users (friends and family) on a bunch of different domains. It's honestly not so bad but yeah, you need a decent dedicated service.
Migrations aren't simple but aren't that complicated either (just did one last year).
I mainly need to copy their email over but it's also a good moment to check they're using decent passwords and to have them freshen it.
I also need to update their webmail and IMAP/SMTP URLs in their bookmark/email apps but I've been playing with DNS CNAMEs for this purpose and it's mostly working ok (aliasing one of my domains to the provider's so I only have to update the DNS which I do anyway for a mail migration).
My mistake was using Google but when it was just the ability to have a personal domain as your google account. But they kept expanding and morphing that into what is now Google Workspace. Migrating people off of that requires them to abandon their Google accounts and start over. If it was just email it would be a much simpler prospect to change backends.
Can you not transfer away a domain from Google as you would from any other registrar? And then set the MX records to point at another mail service?
Certainly. But, what I'm trying to say is it's not just email. My users are using my domain as their Google account. All Google services, oAuth, etc..., not just email. To do it right I need to get them to migrate their google services to a gmail.com account.