It’s not weird. I’d appreciate it if it were me.
Just wonking about on the internet… oh look, a bee.
It’s not weird. I’d appreciate it if it were me.
Contratulations, you’re the inaugural aroo
Tell me there’s a switcheroo community/magazine
I just bought an actual domain and use that 😅
As an added bonus, letsencrypt works with no effort.
When it’s running in server mode it provides a similar UI too when it’s a client, except now you can browse the snapshots/policies of each client that uses it.
Not quite full management but yeah, good for home use.
My vote goes to Kopia.
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.
I’ve seen lovercraftian nightmares
I love this.
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.
Yes, but WordPress !== PHP. It’s one of the worst examples of what PHP can look like and they resolutely refuse to adopt modern standards or improve in any way. They still use SVN too. Bunch of backwards troglodytes.
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.
For an organisation hosting as many companies data as this one I’d expect automated tape at a minimum. Of course, if the attacker had the time to start messing with the tape that’s lost as well but it’s unlikely.