Alvaro's answers hit the nail on the head. To make it as simple as possible, you version your box by rolling the new box with the version in the box name, then you make this new version accessible to your users by updating the metadata.json file stored on the server "near" your box with a link to the new box in the appropriate JSON structure (see his links for examples). Your users' Vagrantfile should have a config.box_url pointing to your metadata.json.
On Friday, May 8, 2015 at 12:39:49 PM UTC-5, John Shao wrote: > > We have a vagrant box that we are storing on a local http server. > "box_url' => 'http://blahbla.box', > > Is there a way to version the box on the remote share so it will > automatically be updated when someone do a vagrant up in the future? > > Thanks > -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
