Anil Madhavapeddy

How about a `carcass install` that could be managed by OPAM and not in `~/.carcass` at all? This would let us make a `carcass-mirage` that can be updated by the...

> P.S. I just warn you that I will have to slightly tweak the body syntax in order to solve #3. Only experimentally using topkg atm so that's just fine...

Would a crunch'ed binary with these static files be useful? Could then try in `iocamljs-it-up foo.ml` and have it magically be served up (or output a static html site). Similar...

I'm testing this today. First refreshing iocaml's dependencies to latest cohttp by getting ocaml/opam-repository#3306 merged.

This is working out great for me. See https://avsm.github.io/ocaml-dockerfile/ for an example site I've deployed using the static site generator. I've got some lashed up scripts that could be cleaned...

That's odd - it seems to be working fine for me with websocket.0.9. The `-js` path munging sounds like a good plan too. I can pull together the `opam-github` plugin...

That makes sense; I was only using JS. Native code is so 2014. > On 3 Jan 2015, at 16:35, Andrew Ray [email protected] wrote: > > The js kernel code...

a mustache port would be awesome!

Yes, we're happy to have contributions to HyperKit that improve its ability to interface with support libraries such as IncludeOS. There is already some scaffolding in there to link to...

This sounds good; please do send in a PR with the JS implementation and I'll fix up the build system to integrate it.