Andrew, Thanks for pointing out the problem in the first place.
The PR adds content-type to the static_website example. I assume this is the same code you built your unikernel from? If so, you already have a git checkout of mirage-skeleton somewhere -- update your config.ml and dispatch.ml from my master [1] and rebuild. To be clear, example code like mirage-skeleton is not managed by OPAM, but its dependencies (like the mirage tool, cohttp, etc.) are. [1] https://github.com/lnmx/mirage-skeleton/tree/master/static_website (It might be a while before my PR gets merged, due to some unrelated build issues.) -- Len On Fri, May 29, 2015 at 4:16 PM, Andrew Stuart <[email protected]> wrote: >>> However, I agree that static_website example could be better in this >>> regard, so: https://github.com/mirage/mirage-skeleton/pull/87 > > That’s a fix, right? That is most obliging, thank you. > > What would I need to do if I wanted to make use of this? Currently I > installed Mirage from OPAM but this probably requires cloning Mirage from git? > > thanks heaps for sorting it out! > > Andrew > > _______________________________________________ MirageOS-devel mailing list [email protected] http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
