suma-project / suma-vagrant Goto Github PK

I am running this on Debian Jessie

vagrant up
Installing the 'vagrant-vbguest' plugin. This can take a few minutes...
Installed the plugin 'vagrant-vbguest (0.13.0)'!
Updating plugins: vagrant-vbguest. This may take a few minutes...
All plugins are up to date.
Bringing machine 'default' up with 'virtualbox' provider...
There are errors in the configuration of this machine. Please fix
the following errors and try again:

vm:

• The 'ansible_local' provisioner could not be found.
• The 'timezone' provisioner could not be found.

The ansible playbook should also install node dependencies for the client dev environment. See https://github.com/suma-project/Suma-Vagrant/blob/master/ansible/roles/development/tasks/main.yml

Hello! Here is my issue:

I am a student worker at the Engineering Library over at the University of Maryland, College Park. We are interested in incorporating this app. I don't have experience with yaml (the error file) and I've tried installing this demo development environment many different ways. The image shows the issue I'm running into. I have a feeling there's a glitch that makes it screw up on Windows. I've tried on two different machines (work laptop and personal laptop) and I run into the same issue.

The localhost loads, but none of the features work. I just get to an internal error when I try to use any of the admin configurations. I tried installing it with the Parallels provider as well, but it doesn't work.

What should I try to do?

Thanks

Hello: I'm trying to install Suma-Vagrant to try out Suma and the vagrant up process is stuck at:

"Clearing any previously set forwarded ports...." (see attached screenshot)

The machine I'm installing on is Windows 7 32-bit with version 5.0.24 of Virtual Box and version 1.8.4 of Vagrant.

Thanks for any help.

After installation tried to bring up suma using 'vagrant up'. Ended up with error shown below

After successfully building and provisioning the vagrant box, running vagrant suspend and then vagrant up breaks the shared folder.

I've got a PR coming that will fix this. Basically, the /etc/localtime on the host machine can be linked to somewhere other than /usr/share/zoneinfo, as it is on my Mac. When the script fails to parse the timezone string correctly, it then fails to set the timezone on the vagrant guest because it is using the full path of the previous link.

Curious about what in ansible playbooks/roles/etc. can not be used to configure a production-ready box? I will review. I see that the guest-ansible.sh script is for development. Also, it looks like account/db permissions might need to be locked down.