vagrant-spk synced folder suggestion

[Nolan Darilek]

Yesterday I tweaked my Vagrantfile for my failing Meteor project, set
/opt/app to rsync, and everything started working. Unfortunately, other
bits of vagrant-spk aren't too happy with my choice. In particular,
"vagrant-spk pack" dumps the spk in /opt/app, then fails to rename it
when it isn't on the local filesystem.

Not sure if this is intentional, but /vagrant is also mounted in the
container. I'm wondering if vagrant-spk might use different mountpoints
for different purposes--/opt/app for actual package construction, so
those of us who need to can set it to rsync, and /vagrant for instances
where it needs to sync something like an spk out of the VM? Not sure
what other parts of vagrant-spk need to pull data out of the VM, but if
they could all do so at /vagrant then that might go a long way toward
solving 2-way sync issues while still letting those of us on broken OSs
build packages in a sane Linux environment.

[Asheesh Laroia]

On Fri, Oct 23, 2015 at 10:05 AM, Nolan Darilek <no...@thewordnerd.info> wrote:

Yesterday I tweaked my Vagrantfile for my failing Meteor project, set /opt/app to rsync, and everything started working. Unfortunately, other bits of vagrant-spk aren't too happy with my choice. In particular, "vagrant-spk pack" dumps the spk in /opt/app, then fails to rename it when it isn't on the local filesystem.

This is an interesting problem. I think the thing we should do is not assume the SPK file shows up on the local filesystem, and adjust how "vagrant-spk pack" works in light of that.

For example, it could always save it to /tmp and then use 'scp' or similar to copy it out. Or maybe it could send it across stdout and we could capture it that way.

 

Not sure if this is intentional, but /vagrant is also mounted in the container. I'm wondering if vagrant-spk might use different mountpoints for different purposes--/opt/app for actual package construction, so those of us who need to can set it to rsync, and /vagrant for instances where it needs to sync something like an spk out of the VM? Not sure what other parts of vagrant-spk need to pull data out of the VM, but if they could all do so at /vagrant then that might go a long way toward solving 2-way sync issues while still letting those of us on broken OSs build packages in a sane Linux environment.

I am not sure what the value is, of having /opt/app as well as /vagrant.

I think the only vagrant-spk component that needs bidirectional sync is vagrant-spk pack, so my preference would be to make that not assume bidirectional sync and then see where we are.

I filed https://github.com/sandstorm-io/vagrant-spk/issues/85 for making vagrant-spk pack simpler for now, at least.

-- Asheesh.