https://github.com/rumpkernel/rumprun-packages/tree/master/p...
We get into tricky situations when you need C extensions, e.g MySQL or PostgreSQL. Since extensions must be statically linked, you have to decide upfront what you want. Either extension can be compiled in, but including both in the package by default.... So a production Python build is fairly custom right now.
Nothing insurmountable, just haven't gotten the workflow perfect.
[0] http://projects.curiousllc.com/flask-in-a-rump-kernel.html#f...
ps - shameless plug but we're hiring talented OCaml devs (http://stackhut.com/#/careers)
pps - Congrats to @amirmc and the Mirage OS group!
The cool part is, if the OS is trimmed down enough (ex < 10mb) it's small enough to fit in version control.
Much like we automate build tools to concatenate/minify web assets, it'll be possible to create a build step that takes a webapp as input and spits out a fully functional VM ready to deploy as output.
It completely inverts the deployment process. Instead of building an environment and deploying an app to it, you focus on building the app and deploy it as a VM when it's ready.
As much as physically possible, yes.