Ever took your embedded system to another place and wondered which network address the darn unit chose and then went the long way to connect display and keyboard just to find out?
Out of that same reason, an exciting new cape component has its debut in this blogpost:
We now have a quite well working zeroconf-based discovery component!
Of course this one only makes sense, if you already use cape as daemon.
It is still in development, so to use it, install the cape.dev package into your cape environment or use the cape install tutorial if you don't have cape, yet.
If you have tkAdmin installed, you can add "cape.dev.discovery" via System/Create Component. Otherwise, add this snippet to your configuration:
In other news, i'm thinking of a way to handle components (and configuration) via command line tools, so adding components or other individualization of your system doesn't require (the somewhat odd) tkAdmin nor throwing around json snippets.
So, stay tuned or help out, if you can't wait ;)
PS: There's promising, yet uncomitted (had a HDD crash, but can recover ;) news on the py3.x front, too! Sooooon…
PPS: I added lots of documentation (esp. tutorials) today.