4 comments

  • avsm1 hour ago
    Nice work! Just looking through the Eio code, you may want to use the capability restrictions more. For example, in the static file serving code, you can use `Eio.Path.open_subtree` which will use Linux fd sandboxing to prevent accidental symlink escapes or other ways to leave that subtree: <a href="https:&#x2F;&#x2F;ocaml-multicore.github.io&#x2F;eio&#x2F;eio&#x2F;Eio&#x2F;Path&#x2F;index.html#val-open_subtree" rel="nofollow">https:&#x2F;&#x2F;ocaml-multicore.github.io&#x2F;eio&#x2F;eio&#x2F;Eio&#x2F;Path&#x2F;index.htm...</a>
  • B4uler51 hour ago
    Will keep an eye on this project, love me some Ocaml! Do you have an example of it deployed and in use?<p>Don’t like the “fresh off the AI block” feeling of the website but could be a bit more confident if I could see it used in the actual wild!
  • andsoitis3 hours ago
    Cool to see some Lisp in this OCaml project:<p><i>Add to your bin&#x2F;dune:<p><pre><code> (executable (name main) (libraries spindle eio_main) (preprocess (pps ppx_wiretype)))**</code></pre></i>
    • mpalmer3 hours ago
      These are S-expressions, not Lisp. It&#x27;s part of dune, which is the build system for ~40% of OPAM packages.
      • andsoitis3 hours ago
        Dune is an unholy combination of bash and Lisp, according to its author - <a href="https:&#x2F;&#x2F;adam-mcdaniel.github.io&#x2F;dune-website&#x2F;" rel="nofollow">https:&#x2F;&#x2F;adam-mcdaniel.github.io&#x2F;dune-website&#x2F;</a>
        • mpalmer3 hours ago
          <a href="https:&#x2F;&#x2F;dune.build&#x2F;" rel="nofollow">https:&#x2F;&#x2F;dune.build&#x2F;</a>
  • sroerick2 hours ago
    Very cool! Congrats. Looking forward to trying