René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"support system NFS as an alternative to UNFS3","articleBody":"There is discussion about this scattered around lots of different issues so I'll try to consolidate it here. Dinghy doesn't use MacOS system NFS because the system NFS server doesn't allow nested exports -- in other words, if you export `/Users/me`, you can't also export `/Users/me/some-other-project`. This is a problem for me and some other people, because we have projects using Vagrant with NFS shares, and so exposing the whole home dir breaks those Vagrant projects. \r\n\r\nBut for those who don't care about that use case, the system NFS server is faster (and probably less prone to issues). I don't plan on adding support myself since I wouldn't use it, but I'm open to somebody else tackling this addition. You'll need to be very careful to lock this down so you aren't exposing the user's entire home dir over NFS to others on the LAN. docker-machine-nfs may make this easier, I haven't looked at it closely.\r\n\r\nAlternatively, it may even be possible to have a daemon listening for Docker events and sharing only specific folders over NFS when they are mounted via Docker, but I suspect it would be difficult to get that working reliably and transparently.","author":{"url":"https://github.com/codekitchen","@type":"Person","name":"codekitchen"},"datePublished":"2018-04-05T16:47:24.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/274/dinghy/issues/274"}