Very cute that there's a one click deployment using some semi-magic third party service, but it feels kinda disingenuous to not link to the repo that's doing the actual heavy lifting.[] The repo submitted to HN is just a bunch of config files.<p>[] <a href="https://github.com/FD-/RPiPlay" rel="nofollow">https://github.com/FD-/RPiPlay</a>
It's good to see Balena getting some attention - it's a really nice way of deploying containerised software to embedded devices, and managing them in the field. I've been using the free tier for managing a couple of rpis I have round the house in a reproducible way.<p>It's basically a whole platform built around docker-compose, so you write a compose file for your different applications and then can deploy it to any embedded Linux computer running the Balena OS. Balena manage all the complicated stuff around rolling out updates, keeping the OS up to date, logging etc, and give some nice debug tooling. The other nice thing about the platform is that it's almost all open source - so if Balena the organisation goes bust or changes strategy, Balena the IoT management service could be self hosted.
Related: If you use Home Assistant and have Chromecast devices, the AirCast addon will allow you to use AirPlay to send something to a Chromecast device.<p><a href="https://github.com/hassio-addons/addon-aircast" rel="nofollow">https://github.com/hassio-addons/addon-aircast</a>
I'm confused as to what "server" means in this context. Does this sit in the middle and mirror other devices (e.g. your Windows or Linux laptop) to a TV/monitor or does it just mirror the RPi itself? Or does it just act as a "sink" for already-AirPlay-compatible devices and let you mirror your phone to a TV without having an AppleTV?
Strange and sad that Apple's approach to remote play is more open at this point than the Google one.<p>Like open IoT protocols, we need to move to open "AirPlay" protocols. The locked-down nature is so pointless.
Chromecasts used to have a free kiosk mode that could boot up to a full screen webpage, then Google gated it behind a monthly device management fee. :(<p>It was cool because you didn't even need another device to run the browser, everything ran on the chromebit/chromebox.
I'd really like some kind of architecture picture describing what runs where. Regardless of whether it's promoting the cloud service why would I want that to run a rPi service?
A picture might explain that.
Looks like basically a deployment setup for RPiPlay, which is an open-source implementation of airplay that's meant specifically to run on a RPI.<p><a href="https://github.com/FD-/RPiPlay" rel="nofollow">https://github.com/FD-/RPiPlay</a>
As I understand it, this allows you to screencast from an Apple device via airplay to an rPi. Is anyone aware of a project that allows you to do the reverse? That is, to airplay from an rPi to some compatible device (like a HomePod)?
Ive been looking for a way to use airplay for my Zwift set up. I have an old raspberry pi so maybe i can set this up to solve it. I am unwilling to buy another apple tv.
Thank you very much, I've been thinking about something like this for a while and have been meaning to look for a solution. Problem solved, thanks!