3 ms·
So, the issue I see here is that the run-from-ram aspect of this limits the use cases for the product. What happens if you want to make changes to files/apps,
by indigodaddy 9y ago
So, the issue I see here is that the run-from-ram aspect of this limits the use cases for the product.
What happens if you want to make changes to files/apps, or are using it as a webserver in conjunction with an SSG and git/CI, etc.
Anytime you want to update you'd have to update some other code on some other http server (which in itself is fine), but then, you'd have to reboot your run-from-ram instance to sync up to your updates/changes (which is the not so great part, IMO).
Am I correct on this assumption, or could this type of scenario work some other way that would prevent an instance reboot? I could be way off here, and only skimmed the bullet points of the website, and that was my first thought/takeaway.
In any case, this seems to be a great way to essentially package live environments as a PaaS, with the added full code customization benefit. Really creative, and hats off to you for thinking of this and providing it for free. Seems there would be plenty of use cases and needs for something like this!
- wmf 9y agoThis is probably based on the philosophy of immutable infrastructure where you never modify a server/VM/container after it has booted; instead you perform a rolling reboot to a new version. It's less efficient but more reliable.
- andrewstuart 9y agoAgreed - the original question is probably best answered via research into immutable operating system deployment patterns. Having said that, when bootrino starts a Run-From-RAM Linux instance, it really is just plain Linux, so how you go about solving the question of deployment is really entirely up to you.