And it's still faster for my linux install to boot.LUKS password for disk encryption, then user login to a usable desktop with network connectivity.Windows takes ages to get to a login screen (bitlocker is disabled, so no decryption excuse), logging in is a breeze with fingerprint reader (certainly faster than typing in a password), then it sits there for ages looking like it's ready to be used, but the network stack isn't ready and it is just unusable until that comes up.
I'm so happy when I get a day of just working in Linux.It just... Works.
I've had one issue in the past year and a half, dual booting from the same NVMe.After fixing the boot partition issues from a liveUSB, the actual solution was disabling fast-boot.It's been solid for a year now.
But I always shutdown my laptop when I'm not using it. And any windows updates that require restarts, I make sure it fully reboots into windows again.
Yeh, I don't quite understand docker desktop.I guess it's handy for seeing running containers, volumes images etc.But I don't get what it offers over CLI, or a TUI like lazy-docker.
You might be thinking of something like portainer, which does let you use compose files via its web gui.
Glad you've figured out the docker compose route. I find config files (and scripts) significantly easier to work with than figuring out a bunch of commands to run.
Yeh, it doesn't look like it's exposing the ports.I don't know docker desktop.I just use docker compose files, even for things that don't need it. I like having a file that describes the service, instead of deciphering run args.
I would strongly suggest you copy the official docker compose file, and run that with "docker compose up -d".That will configure all the components required, then you can still inspect/stop/start/view etc using docker desktop.
But I also understand the brain fog.Maybe you could work through the fog to install Portainer once. After which, you can use that and it's web GUI to manage all your containers and compose files.Setup on Windows/WSL with Docker Desktop (but needs 2 commands: 1 to create the volume, 1 to run the container)
https://docs.portainer.io/start/install-ce/server/docker/wsl
Portainer might be more what you are looking for, rather than docker desktop (although docker desktop does make docker installation a lot easier)
Reading https://github.com/wallabag/docker I don't see any mention of doc75/wallabag as an official image.
Any reason you went with a 3rd party image?
Also, might be that you aren't exposing the port? Wallabag looks like it runs on port 80. Might be that port 80 is restricted (or in use), so docker desktop can't bind it. Maybe forward a random port to it.
You can also inspect the container. It will show env vars, networking binds, volume binds etc.Make sure they align with what's in the official docker-compose. Once you get that working, you can start tweaking towards your requirement.
I use it for scripts or for esoteric error messages or problems I'm having in my dev environment.I can't be bothered to understand a specific error message that I've never seen before because of an update or whatever.So getting it to explain errors to me is handy.I always review the LLMs process and the resulting changes it suggests (including searching what it's done if I don't get it).It's essentially a context-aware search engine.
Yeh, why not make billing able to carry ages verification?Banks have to verify their customers. They (mostly) have a history of handling data well, it's in their interest/requirement to continue doing that.The banking sector is well regulated compared to software/startups.
That can remove a large amount of service providers suddenly needing age verification. Just rely on the service purchase to verify it
All official reporting indicates a well mannered race between candidates.The correct and best leader has been chosen fairly by all citizens.And all opponents now also agree, as do their voters.
Musk runs a service that gives internet everywhere and has the ability to pinpoint the ground access point precisely, as well as requiring a billing account to access.You can't use starlink without the service provider knowing.
You can use cheap, 2nd hand, outdated, whatever network equipment to create your own local network without anyone knowing. It can be entirely airgapped and still work.
Unifi/Ubiquiti point to point radio kit is extremely easy to get hold of an can be used entirely airgapped (because it's on the border of pro & consumer level kit).That's like saying "Russia is using ethernet cables" or "Russia found to be using intel NICs" or "Russia found to be using Mellanox SFP modules".That can't be restricted.
The ability to tune in a point to point wireless network and maintain that ALL the way to the frontline takes skills. Any mid station can be targeted and isolate a bunch of frontline networks. Running multipath redundancy links is a significant challenge.
The ability to drop something on the ground and have instant internet access anywhere (starlink) is not a skill. It's an enabler, and musk enabled.
The person in the middle would be supporting twice the weight of the person over the hole, and they would have to do it twice.The person over the hole and the person not over the hole just has to hang on.
When the middle person is over the hole, the people at each end support half the weight of the person over the hole.
The length of the pole doesn't matter, as long as the person in the middle is in the middle of the pole and that the pole is more than twice the length of the hole.If the pole was significantly long enough, then the force on the middle person could be reduced significantly, but it will always be more than the weight of 1 person.
It doesn't.Have you ever been ddos'd? I haven't.I imagine if it happens, I'll just switch off the VM.If it's actually a problem, then I'd see what the VM hosting company recommends. Ultimately they will have something in place so that if my VM gets targeted they can isolate it.My sites get denied service. Oh well.
I've never had anything get so popular that I actually need the tooling that cloudflare offers. I've never had anything targeted in a way that cloudflare would protect against.
If that is actually a vector in your security and reliability analysis, then yeh. It's probably the right tool for it.And there are other competitors than just cloudflare if you actually need the protection, which should each be considered.
And a VPS and any number of tunneling systems for the remote reverse proxy.Rathole is my goto. But SSH forwarding, wireguard... There's plenty, even ones that will entirely manage the reverse proxy on the VPS.
"It's just the data we need to protect our business. It's legitimate interest, I promise"