.dev domains are required to only be reachable via https. You've not mentioned that in the post, so I'm guessing port 443 is not serving or even listening.
I'd delete the screenshot with your IP visible. You never know...
Rent a domain
Set up email
Use a unique address for every website
I usually pick the domain of the website as the username part.
So if, say, I have email set up on lemmy.cafe and want to sign up to flatearth.com - I'd probably use flatearth.com@lemmy.cafe for an email address. If they ever leak it - I'll be reveiving spam sent to this address.
In the six years of hosting my own email I've only had one such occurence when namecheap got breached. It was nice being able to tell where the culprit was!
If you're dead set to run lemmy - then just do it! If soam becomes a problem - turn on registration verification. Spam usually comes in waves, so you don't even have to keep that barrier on all the time. Having said that - if you want some sort of nationality verification - application process could enable it.
If you're not set on lemmy - give piefed a shot. That's what I would run if I were setting up from scratch. Same format social media, but, at least from what I'm hearing - better software.
Setting up is easy, but keeping it up to date is often troublesome. Releases are far and few between and as such, whenever there is one, it includes a lot of changes. That leads to some instances having trouble pretty much every time; I've been on the unlucky side enough times to be wary.
Lemmy.cafe runs on 2 dual vcore 4gb ram VMs on digitalocean - one for db, another for lemmy itself.
Lemmy prides itself in being written in rust, but it leaks memory like a sieve - I've had split up the containers into smaller tasks (there's an official flag you can pass to it), double them up and set memory limits. That way when something gets killed by the kernel it's not really noticable to the end user.
Running a public instance of anything is a security concern, let alone alpha-beta software like lemmy. If you do run it on your homelab at home - at least get the cheapest vm in the cloud to hide your home IPs. You'd probably need to set up a wireguard tunnel to ensure outgoing federation does not reveal the IPs to other instances.
Instance level moderation is up to you. Don't be too dreamy - nobody will join your instance just because you have it running. Other than spammers and voting bots, that is. Moderation tools are just not there, so you'll have to fiddle in the db directly.
Having said all that - if all you want is a personal inatance - go for it! With sign ups disabled it's a much less stressful experience!
Majority of openrc/hardened/selinux binhost setup is done, need to figure out the small things.
Lemmy was also giving a bit of a headache, fiddled with limits some more.
I'm fairly certain there's been an attempt to play with some opnsense config, but there was only time to install the updates. Or maybe this was last week 🤔
Whole path has to be accessible, not just the file itself. All dirs above the file need to have the executable bit set that affects the user accessing the file.
An ebuild is a definition - a recipe, if you will - of how a package is built from some source by portage, a Gentoo package manager.
Very few things are trully impossible in linux land, but having multiple package managers on a single system is just asking for trouble.
You could try setting up a gentoo prefix and get the benefits of portage that way, but I've not beem able to accomplish that the single time that I tried.
.dev domains are required to only be reachable via https. You've not mentioned that in the post, so I'm guessing port 443 is not serving or even listening.
I'd delete the screenshot with your IP visible. You never know...