Pros:
- Maintained by Vagrant, so easier to maintain. Also, this will have
more testing and user feedback backing it than our customized
vagrant-sshfs plugin will have.
- Works out of the box, just one `vagrant up`
- No tinkering required on the Windows host (but NFS server required
on Linux and Mac hosts)
Mac has smb built in afaik. don't know about NFS - but if users need
to
install it this feels doomed since
we already have a ton of other things that need to be configured.
Vagrant configures everything on the host, be it SMB or NFS, no
configuration required.
I'm confused - "but NFS server required on Linux and Mac hosts" implies
to me that you
or the user will need to do some install or setup (i.e. configuration)
for this to work ?
Steps for Windows:
- `vagrant up`
- `vagrant provision`
- `vagrant reload`
Steps for Linux:
- Allow incoming connections to the NFS server on the host
- `vagrant up`
I'm not following why the steps are different between the OS's here ?
And if users need to learn to run all three vagrant
up/provision/reload
and different between OS's this is bad/not good either ;/
There is only one step i.e. `vagrant up`, the extra ones are there
because cifs-utils has not been packaged in adb vagrant box, yet!
Okey.
/max
http://about.me/maxandersen
_______________________________________________
Container-tools mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/container-tools
