Hi, Thanks Holger for your recipe. It works fine when the .json file is on the local filesystem but not if I try to access it through ssh. I already documented my issue on your recipe's issue tracker https://github.com/hollodotme/Helpers/issues/2 but ask the question here in case somebody has got the same problem as me.
Is this a known issue in vagrant? Le vendredi 30 janvier 2015 08:11:45 UTC+1, Ryan Doyle a écrit : > > I just wanted to say thanks as well! I was previously versioning my boxes > by having the version in the name. I've now moved this over to use the json > format you've described. > > On Wednesday, July 30, 2014 at 6:02:44 AM UTC+10, Holger Woltersdorf wrote: >> >> Hey there, >> >> I came across these issues, questions and missing documentation, too. >> After diving into this subject for a couple of days, I wrote a (long) >> tutorial about these topics. >> >> You can find it here: http://bit.ly/1uEs7GS (GitHub) >> >> Espacially the chapters 4 and 5 should basically answer your questions / >> give you an idea of how to self-version and self-host vagrant boxes. >> >> I hope this helps! >> >> Am Montag, 19. Mai 2014 09:29:19 UTC+2 schrieb Ryan Parman: >>> >>> I can't seem to find any documentation about leveraging Box Versioning >>> without Vagrant Cloud. My company currently keeps it's Vagrant Boxes in S3 >>> and we'd like to continue using that. >>> >>> Can you point me to some documentation (if its available)? There's >>> nothing here: http://docs.vagrantup.com/v2/boxes/versioning.html >>> >>> -- 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.
