It’s not weird. I’d appreciate it if it were me.

I just bought an actual domain and use that 😅

As an added bonus, letsencrypt works with no effort.

It’ll never happen, centralised means stable. Just check out what this company called Google have built!

Not true.

Both Lemmy and KBin map the same activitypub activities to the same upvote and downvote actions.

Came here to comment this “obscure” combination. That I use. Lol

Kopia is a solid bit of software. I run it on my VPS’s, my homelab and my desktop/laptops. All to a single Backblaze repo.

As the “owner” of a community an instance is responsible for distributing posts made to it to other servers. Beehaw have said they’re not listening to lemmy.world and so don’t distribute posts made by lemmy.world users.

Not to mention that the defacto package manager (composer) blows NPM out of the water in basically all metrics. From what I understand most languages package managers now look up to or even model themselves on it.

Large parts of my particular departments .gov.uk stack are PHP. All modern (8.1+) using established frameworks and to be honest, it’s a joy. It’s quick to write, easy to understand and very easy to test. The write, run, debug cycle is also essentially instant; although I really enjoy using Go (another bit of the stack) being able to quickly iterate changes is something I absolutely miss when I’m using it.

Laravel + Livewire is some sort of dark voodoo magic. I can write only PHP and have a functioning SPA with push updates and all sorts.

There are tests (and if the readme is to be believed a 71% coverage) they live in the top level tests/ folder.

As to the .env file you just need to rename the example one and either amend these values (with appropriate urls)

SERVER_NAME=localhost
KBIN_DOMAIN=localhost:9443
KBIN_STORAGE_URL=https://localhost:9443/media

MERCURE_URL=https://localhost:9443/.well-known/mercure
MERCURE_PUBLIC_URL=https://localhost:9443/.well-known/mercure
CADDY_MERCURE_URL=https://localhost:9443/.well-known/mercure

Or add them to a new .env.local file.

Start it all up and jobs done*

*well, you need to run the asset pipeline and add an admin user but that’s all in the Readme.

It has one. Minus an undocumented step (that’s sat fixed in a pr). Bringing it up amounts to 4 lines in a console; 1 to bring up the stack and 3 to start a JS watch for asset compilation.