Local DNS with rewrites is the answer. Don't mess with CoreDNS unless you know what you're doing. It has the potential to fubar the cluster DNS.
Running a local DNS server is super easy, especially compared to managing a kubernetes cluster. Install Adguard Home or Pihole, set your devices to use this server, and add some rewrites. That's it.
A good rule of thumb, stay away from Pixels that came from Verizon. AFAIK they're the most hostile US carrier and their Pixels cannot unlock the bootloader.
I've been setting up a baremetal Talos-based cluster on 4 SFF machines and using Flux to declaratively deploy things to the cluster. Once you wrap your head around how Flux operates, deploying things becomes fairly straightforward.
For me, the most difficult process was deploying the cluster properly, but the recent-ish video posted on the Tailscale YT channel helped a LOT.
I went the nuclear option and am using Talos with Flux to manage my homelab.
My source of truth is the git repo with all my cluster and application configs. With this setup, I can tear everything down and within 30 min have a working cluster with everything installed automatically.
As long as your important data is safe, go mess things up. Break things, read the docs, reinstall if necessary. This is how we all learn.
I can't count the number of times I've had to reinstall because I attempted a fix that made things worse. It's not the end of the world... In fact each time you do you'll be better at it.
When your data is safe (backed up or stored on a NAS) the reinstall stakes are a lot lower so there's not as much pressure to keep things perfect. Figure out how to automate your computer's config (I use ansibe) and it's even lower. When that is setup you could reinstall and be ready to go in under an hour.
Most of the time you can pick up badges afterwards on second hand markets, sometimes defcons official shop has some leftovers.
I have a strong feeling the chips will be available for purchase afterwards. This whole thing feels like a product launch.
Local DNS with rewrites is the answer. Don't mess with CoreDNS unless you know what you're doing. It has the potential to fubar the cluster DNS.
Running a local DNS server is super easy, especially compared to managing a kubernetes cluster. Install Adguard Home or Pihole, set your devices to use this server, and add some rewrites. That's it.
https://i2p.net/en/docs/
This might help.
Might be time for a firewall device to be added to your network.
A good rule of thumb, stay away from Pixels that came from Verizon. AFAIK they're the most hostile US carrier and their Pixels cannot unlock the bootloader.
I really want to like Cosmic but there are too many usability papercuts for me at the moment, so Gnome it is.
You're right.
If you login to Vaultwarden and access the Web vault, is there a path like
/adminyou can add to your blocked paths config?If you're deploying Vaultwarden via docker, there's an ENV to disable web vault
Set to false and redeploy.
I'm in the same boat. Considering swapping out for a Linux based media box instead of the AppleTV.
Use homebrew for Linux.
Orion browser.
Logseq. Have used it for years. Sync across devices via syncthing. Since its all markdown files there should be no issues.
Need to restore? Copy files to new location, point the program at the new folder and you're good to go.
I've been setting up a baremetal Talos-based cluster on 4 SFF machines and using Flux to declaratively deploy things to the cluster. Once you wrap your head around how Flux operates, deploying things becomes fairly straightforward.
For me, the most difficult process was deploying the cluster properly, but the recent-ish video posted on the Tailscale YT channel helped a LOT.
Iirc Verizon doesnt sell Pixels that can unlock the bootloader.
I've got a forgejo instance setup but I haven't migrated everything to it yet.
I went the nuclear option and am using Talos with Flux to manage my homelab.
My source of truth is the git repo with all my cluster and application configs. With this setup, I can tear everything down and within 30 min have a working cluster with everything installed automatically.
As long as your important data is safe, go mess things up. Break things, read the docs, reinstall if necessary. This is how we all learn.
I can't count the number of times I've had to reinstall because I attempted a fix that made things worse. It's not the end of the world... In fact each time you do you'll be better at it.
When your data is safe (backed up or stored on a NAS) the reinstall stakes are a lot lower so there's not as much pressure to keep things perfect. Figure out how to automate your computer's config (I use ansibe) and it's even lower. When that is setup you could reinstall and be ready to go in under an hour.
Therapy.