Do I miss something? How do you adopt the device in the first place? If you have to SSH into the device and set the inform URL manually could't you just route the request based on the request hostname?
Yep, once you set-inform the host header handles the routing. This in particular is most useful for things like DHCP Option 43, where devices only get an IP.
We support two approaches, you can either pre-register MAC-Addresses or you can add source IP's to assist with that mapping. There is more information in our docs about this: https://tamarack.cloud/docs/migration
same here. newer saw such a fleshed-out ssh thingy. i just HAD to buy it. a bit weird to see this story on the frontpage now, just ordered tons of techy stickers from AliExpress two days ago...
i must say that the shopping experience on stickr.shop is way better than Ali, haha.
Yes, there's us over at https://garden.io! We're big believers in pipelines that run anywhere. I even made a short little video that should give you the gist. [1]
Some of the short-list of differences: we use YAML for our configuration language, Dagger can use full-fat languages to define its pipelines. Our feature scope is broader: you can use us to vend IDP-like stacks to your developers if you're a Platform Team; we make development with remote Kubernetes clusters very easy, including all the remote image builds; and we have a number of integrations so you can bring your IaC tool of choice (Pulumi, Terraform) into your pipeline and set up service -> infra dependencies.
Hey, Dagger employee here. This exactly is one of the the main design decisions of Dagger. We're not expecting companies and/or projects to perform a full migration to it, that's why we generally recommend starting by wrapping different parts of your pipeline and move on from there. Unlike other solutions, Dagger allows you to keep using your existing tooling and reuse Dockerfiles (https://docs.dagger.io/quickstart/429462/build-dockerfile/#r...) while slowly transition your pipelines to code.
Sometimes people find just starting with a messy part of the build process, or starting to replace dockerfiles here and there can add value, without having to change the world.
As long as your Proxmox Cluster is backed by shared storage (ceph, gluster etc.) and HA is configured for your opnSense VM you can just shutdown the Node. Works flawlessly with pfSense (PVE backed by ceph).
Ok, It's slowly coming together. So I assume I'd then put the virtual WANs of each cluster node on the same VLAN and whichever is currently hosting the router would chat with the PON to give me a WAN link.
Nothing is true if it's not on a piece of paper in Germanys Healthcare System ;) We sadly print through multiple sliced trees in a year. Can't wait for the whole system to be digitalized. There's so much work that could be automated if nobody needs to carry paper around.
Ah! Anecdote; a friend of mine had an issue in Dresden for which they needed his Dutch health records; the Dutch public clinic sent an ambulance with 2 drivers to Dresden to deliver them on a cd. And then left again. The German doctors were absolutely flabbergasted how backward NL was in that regard. They said why don’t they just email an encrypted version? Not allowed. Summer of 2020.
reply