Ethereum Community Forum
Home› Projects
Vega Finally Unleashed! Fine-tuned performance and power consumption in a single chassis.

Vagrant/Ansible virtual box for dapp development

jesus666jesus666 Member Posts: 62 ✭✭
edited August 2015 in Projects
https://github.com/jesuscript/vagrant-dapp-env

What can you do with this?

vagrant up

Give it a minute or ten. Voila! Now you've got a virtual machine with geth, pyethereum, solidity compiler and embark running on your system. SSH in and start building! (read the docs first!)

vagrant ssh


This is version 0.0.1. More stuff, like meteor will come later. Feedback is appreciated ;)
Post edited by jesus666 on
· Share on TwitterShare on Facebook

Comments

  • caylorcaylor Member Posts: 25 ✭✭
    Set this up on my machine today and was pleasantly surprised to find that it mostly still worked. It failed when cloning pythereum for some reason but I switched this out for webthree-umbrella and then ran 
    vagrant provision --provision-with git
vagrant provision --provision-with shell
    to complete the provision script.

    Thanks very much for sharing. Are you coding your DApps on the host machine and then pushing from the DAPPS folder to the Vagrant VM to run the DApp against the test net? If so, how do you sync it or is this automatic?

    What kind of issues have you run into?
    · Share on TwitterShare on Facebook
  • DaedalusDaedalus Member Posts: 36 ✭
    It'd be awesome if this was still in active development. With the recent rise in Etherum popularity, hopefully it will.
    · Share on TwitterShare on Facebook
  • caylorcaylor Member Posts: 25 ✭✭
    Played with the box a bit more tonight. As the files are shared between your host machine and the Vagrant box in the DAPPS folder, it's impossible to create a Meteor application in this folder and then run it because the Mongo DB cannot lock files.

    https://github.com/ethereum/wiki/wiki/Dapp-using-Meteor#create-your-Ðapp 
    [email protected]:~/DAPPS/gigg$ meteor
[[[[[ ~/DAPPS/gigg ]]]]]                      

=> Started proxy.                             
Unexpected mongo exit code 100. Restarting.   
Unexpected mongo exit code 100. Restarting.   
Unexpected mongo exit code 100. Restarting.   
Can't start Mongo server.                     
MongoDB had an unspecified uncaught exception.
This can be caused by MongoDB being unable to write to a local database.
Check that you have permissions to write to .meteor/local. MongoDB does
not support filesystems like NFS that do not allow file locking.
    I suppose I could run a cron tab to copy the files across to a useable folder periodically.
    · Share on TwitterShare on Facebook
  • caylorcaylor Member Posts: 25 ✭✭
    The answer to the db issues; create a symlink.
    · Share on TwitterShare on Facebook
Sign In or Register to comment.