Stéphan Kochen

I've fixed some of the issues from the original attempt: - Now doesn't install workspace dependencies that weren't referenced by the subpackage being built. This new approach adds a `deploymentConfig.packageOverrides`...

I've extended the implementation to create symlinks when running node2nix on the workspace `package.json`. The `WorkspaceSource` now has a `symlink` flag, and these sources generate Nix with a string `symlink`...

Yarn workspaces are not supported by npm, no. So some of the obstacles are to be expected. The idea to try Yarn workspaces was to see if it'd highlight similar...

I think `Response::map` might work for you? https://docs.rs/http/1.0.0/http/response/struct.Response.html#method.map Alternatively, you can do `into_parts` + `from_parts`: https://docs.rs/http/1.0.0/http/response/struct.Response.html#method.from_parts Both should allow you to create a new `Response` with a different body type,...

I like that idea! I'm also kinda torn about certain issues that have popped up since I started using NFS. Apparently, there's some extra check in the Docker daemon that...

I took a brief look at this as part of #24, but didn't try to implement it. Not sure why. Maybe because I too discovered Rust support is currently limited....

I guess we should have both benchmarks in code somewhere, but I'll stick to `ab` for now, because it's what I have. :) Using `block_in_place` requires `rt-threaded`, which totally changes...

Woah, I was testing this, and just now noticed there's some sort of protection built-in: ``` # docker run --rm -it -v $HOME/foo:/foo debian:jessie /bin/bash docker: Error response from daemon:...

Unfortunately, there are no such options. I think I read somewhere the OSXFS behaviour is to store VM permissions inside extended attributes on the host, and where the attributes is...

Yeah, the `uid`/`gid` mount options don't seem to work for nfs: ``` # mount -t nfs -o noacl,noatime,nolock,async,uid=501,gid=20 192.168.65.1:/Users /Users mount.nfs: an incorrect mount option was specified mount: mounting 192.168.65.1:/Users...