Provide a Vagrantfile to allow for easier development about sandstorm HOT 15 CLOSED

I believe the link you are looking for is: http://cloud-images.ubuntu.com/vagrant/saucy/current/saucy-server-cloudimg-amd64-vagrant-disk1.box from http://www.vagrantbox.es/

from sandstorm.

Thank you @jsilvestre that does look like it

from sandstorm.

Hmm, I think I'm going to have to sit down and learn how to use Vagrant so that I can properly review this. For now I'll leave this issue here so people can find it. Thanks!

from sandstorm.

I would be glad to help you:

1. Navigate to http://www.vagrantup.com/downloads.html and choose the package for your OS
2. Navigate to https://www.virtualbox.org/wiki/Downloads and choose the package for your OS
3. Install VirtualBox (which is a great piece of software to have lying around anyway)
4. Install Vagrant
5. Download the Vagrantfile mentioned above into almost any directory you'd like. The caveat is that Vagrant will create a .vagrant directory in the same directory that the Vagrantfile lives, and Vagrant will also name the virtual machine with the directory name as a prefix. These might be minor things, but just be aware
6. Change to the directory containing the Vagrantfile
7. Type vagrant up
8. Vagrant will emit messages from its provisioning process (which will include downloading that file that jsilvestre helpfully found for me and placing in $HOME/.vagrant.d/boxes) and then subsequently the messages from cloning and compiling all the sandstorm pieces.
9. At the end one should see the Good luck! message from the Vagrantfile provisioning script, at which point Vagrant is done and the vm is running and ready for use.
10. Again in the same directory as the Vagrantfile, type vagrant ssh and it should log you in as the user vagrant on that machine, where you can cd ~/sandstorm/shell && meteor and the rest should look familiar :-)
11. To stop the vm, one can use the normal shutdown -h now or from the host terminal vagrant halt or the more destructive vagrant destroy will stop and delete the provisioned vm (but not the template box that it downloaded)

Please let me know if I can help further!

from sandstorm.

I noticed an error in the vagrantfile https://gist.github.com/mdaniel/9776375#file-vagrantfile-L108: it should be box_url instead of url (reference: http://docs.vagrantup.com/v2/vagrantfile/machine_settings.html) :)

from sandstorm.

I've started the Vagrant box provided by your script and I'm wondering now how I can start playing with Sandstorm. I've seen the port 3000 isn't forwarded and from the VM CLI, curl http://localhost:3000 doesn't respond.
Any hint would be highly appreciated! Thanks in advance!

from sandstorm.

Thanks @jsilvestre for catching the typo; that'll teach me not to make random edits to a gist without trying it. :-)

I have not studied the port forwarding syntax primarily because I use the host-only addressing scheme to have open access to the machine via its host-only address. That section is commented out because I didn't want to clash with another IP by default.

It is pretty weird that the curl localhost didn't respond, though. I'll fire my sandstorm box back up when I get to work and see what success messages should appear. I'll also look up the port forwarding syntax and see if I can make that work, too.

Thanks for trying this out; it's always hard to know what assumptions I am making and this is exactly the kind of feedback I would want in order to make booting up sandstorm a truly painless process.

from sandstorm.

Regarding port forwarding: we've used this with success in another project: https://github.com/kaos/zotonic-vagrant-tutorial/blob/master/Vagrantfile#L20

edit: only 15 seconds apart... :p

from sandstorm.

I can help with that too:

config.vm.network "forwarded_port", guest: 3000, host: 3000

edit: oh I believe I was typing when @kaos wrote his post, sorry for the double!

Regarding my issue it seems that the provider hasn't run itself in the first place, vagrant provision did the trick even if it failed because my VM doesn't have enough memory apparently (booh, slow computer :-/). When I tried again, it didn't work because there was conflict, I don't know if it's something you can avoid or not (haven't checked your script in details).

From now on, I keep getting "Timed out while waiting for the machine to boot" while vagrant up so I guess I'm going to raise the timeout (config.vm.boot_timeout) to something bigger than 300s (default).

from sandstorm.

Don't forget to forward ports 7000-7100 as well, since those are used for hosting apps.

from sandstorm.

Today has been a very, very bad day at work, so I have not had time to look into this (and don't expect I will in the immediate future). But I will try very hard to circle back to this.

Also, feel free to fork the gist if you know the things to type and you find a configuration that works better for you. For example, maybe the memory allocation of 1024m is too much and should be scaled back to 512 or such.

from sandstorm.

Hey everyone,

Sandstorm now has an installer script, described in the readme. Shall we revise the Vagrantfile to use it? It should simplify things quite a bit.

I can modify the installer to support a "no-prompt" mode where it assumes the default answer to every question, if that helps.

from sandstorm.

#20 now contains a pull request that takes suggestions from this thread, particularly including:

• Use the bundled install script.
• Forward ports 7000-7100.

Note that I had to modify the install script accordingly.

from sandstorm.

I've now merged @paulproteus' change, so I think this issue is resolved! :)

from sandstorm.

When I tried to vagrant up today I got a 404 error for the box url. I've created a PR to point to the "current" URL, which I assume won't change: #47

from sandstorm.