So, I have to download, as per official discourse development guide, vagrant software and then, run vagrant up in the git shell opened from the github desktop client for dicourse’s master branch. My question is I get something like this: [Bild] The problem is that my internet connection is not ve…

[Bild] GaurangTandon: My question is: How can I download that .box file and complete all tasks that vagrant up does without using cmd? Download http://discourse-vms.s3.amazonaws.com/discourse-1.3.0.box Run vagrant box add discourse-1.3.0 /path/to/the/downloaded/discourse-1.3.0.box

EDIT: This error got solved down below Thanks! The file got downloaded completely, but I got this error. I don’t know why. Please help :slight_smile: [Bild]

You should use “\” instead of “/” as separator on Windows :wink: It should be vagrant box add discourse-1.3.0 C:\Users\intl\Desktop\discourse-1.3.0.box

I am sorry but I don’t really understand cmd well :confused: and so need some more help, well, because, now, I got this error: $ vagrant box add discourse-1.3.0 C:\Users\intl\Desktop\discourse-1.3.0.box I:/Vagrant/embedded/lib/ruby/2.2.0/uri/rfc3986_parser.rb:66:in `split': bad URI(is not URI?):fil…

Try this vagrant box add discourse-1.3.0 C:\\Users\\intl\\Desktop\\discourse-1.3.0.box Or this vagrant box add discourse-1.3.0 'C:\Users\intl\Desktop\discourse-1.3.0.box'

Same error that I got the first time: [Bild] I have double checked, the .box file exists at the path I have specified in the cmd above. Seems like I have to re-download the file, isn’t it?

It looks like you are on the “F” drive (?) and is trying to access file on the “C” drive. Windows path is notoriously peculiar. I would suggest you move the file to a location that you can reference using a relative path. Try to use .. to trace to your file and avoid referencing it using C:/

Ok, my discourse folder (that I had cloned from the main site) was on F drive. And my .box file was on desktop. I moved the .box file inside F drive, so that discourse folder and .box file were siblings inside F drive. And this time, using relative paths worked: vagrant box add discourse-1.3.0 '..\…

Ok, so according to the next step on the official guide , I ran vagrant ssh next but things didn’t go as expected. Here’s what happened: [Bild] Any ideas why?

Run vagrant box add discourse/discourse-1.3.0 '..\discourse-1.3.0.box' instead of vagrant box add discourse-1.3.0 '..\discourse-1.3.0.box'

`vagrant up` not from command line?

Entwickler

zogstrip 18. März 2016 um 11:35 2

Download http://discourse-vms.s3.amazonaws.com/discourse-1.3.0.box
Run vagrant box add discourse-1.3.0 /path/to/the/downloaded/discourse-1.3.0.box

Thema		Antworten	Aufrufe
Error while running vagrant up Development	3	2381	5. Mai 2017
Vagrant installation requires wget Development	1	1367	23. Mai 2017
»vagrant up« hangs Development	6	1865	5. April 2018
Vagrant up fails with "HTTP/2 stream 1 was not closed cleanly: INTERNAL_ERROR (err 2)" Development	2	3154	5. Mai 2017
Vagrant 1.8.7 will not download image. Reverting to 1.8.6 will work Development	3	1270	29. November 2016

`vagrant up` not from command line?

Verwandte Themen