Show HN: Resin.io – Push Updates to Linux Devices with Git and Docker
resin.io
resin.io
A couple questions from a potential future customer:
* What are the bandwidth requirements for your agent?
* Has your agent had any issues with restrictive firewalls?
* How long until you think you'll have the container diff functionality finished? (We are on cellular connections mostly, so bandwidth is somewhat expensive.)
* How much funding/runway do you guys have? What would happen if you guys had to close down the business for whatever reason?
* Pricing? (Couldn't find it on your site.)
Diffs and other improvements that affect bandwidth requirements should be complete in the next two months, before we announce pricing. Our agent requires standard web ports, so a firewall that allows web browsing should allow a device to connect. We are funded by a well-known Silicon Valley VC, this will be announced in a few weeks.
Pricing isn't finalised yet (will be announced in 2 months) but drop me an email at alexandros@resin.io and I'd love to let you know our current thinking.
Reason I ask is last I checked Docker is only for 64 bit processors, and beagle bone black runs a 32 bit processor.
I guess if I used Docker it wouldn't matter what language is running in the container, but it would be nice to have that confirmed.
Does resin.io handle the differences in GPIO-pins btw? I have both rev1 and rev2 Raspberry today, and make sure to not use the GPIO-pins that they have mixed around between the different revisions.
we do abstract networking control as resin is dependent on the network to keep operating, but the application can take control (and responsibility) of networking if needed.
- Do you plan to contribute changes to upstream projects (e.g. Docker for ARM), or open source other parts you have developed?
- Will you have a pricing model / level that's works for small scale private projects?
Thanks
Is there a timeline for Intel Edison support?
thanks!