Create a resin.io account to archive and distribute embedded device contents for DoES

[MatthewCroughan]

@DoESLiverpool/directors

@ajlennon Suggested I ask you about this.

We have the door bots on Github, and that's fine, but it would make sense to start backing these up on something like Resin.io, may come in handy for more easily creating distributed setups in the future too. This is more about the future than modifying the existing set up. If I'm going to make a calendar for the entrance based on resin.io, it would make sense for other embedded things to be located there too.

#903

[amcewen]

I'm not against us having a resin.io account, but I don't think we should be starting to adopt it more widely given it costs $99/month once you get to 10 devices. Given the calendar device, five doorbots, one for the MQTT gateway, then the Pi managing the network, that's already 8 devices you could argue for, and that's before any of the cameras which presumably are also going to be resin.io devices...

In contrast, the doorbots are on github with (mostly) automated ansible scripts and cost us $0/month. It took me about an hour per doorbot to provision a new one.

[ajlennon]

I don't think we'd want to migrate existing devices over would we? We're just looking at Live Streaming cams at present... And possibly output Displays.

"We'll never need more than 4 of these computers anyway..."

[skos-ninja]

The problem is though is if we do go over the limit at some point we will have built tooling around something that price wise isn't feasible to keep.

…

On Mon, 1 Oct 2018, 13:37 Alex Lennon, ***@***.***> wrote: I don't think we'd want to migrate existing devices over would we? We're just looking at Live Streaming cams at present... And possibly output Displays. "We'll never need more than 4 of these computers anyway..." — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#933 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGVbXzBAvnfgQgIQuIIJNyWtLTrt3Qreks5uggx8gaJpZM4W_mb2> .

[ajlennon]

Googling around Resin.io have reiterated their commitment to an OpenSource equivalent to their cloud platform, delivered some time around now. So this looks like a good way forward to keep an eye on

https://resin.io/blog/open-source-resin-io-progress-and-next-steps

[ajlennon]

I've been doing some documenting if anybody fancies setting one up. Would appreciate any feedback on mistakes...

https://github.com/DynamicDevices/makespacelive

[ajlennon]

I've documented a standalone install and a resin.io install.

There's not much to it

• base image
• dependencies
• compile a RPi specific GStreamer1.0 plugin
• script

Have you got some time to run me through how I would convert my Resin.io Docker file to Ansible @amcewen ?

[amcewen]

Happy to show you the ansible stuff sometime. There's not too much to it, it's mostly a way to script ssh (or at least, that's an easy way to approach it). If you clone my handy-ansible-roles repo the README.md will give you the basic steps to get up and running with a Pi

[DoESsean]

Is this still a thing? I have no idea what any of it means, tbf.

[ajlennon]

Resin.io is now called Balena.io and now has an OpenSource release - I'm working to get a build of this installed on my public facing IP address for testing. It's under active development atm