- **status**: open --> closed - **assigned_to**: Dave Brondsema - **Size**: --> 2 - **Milestone**: limbo --> forge-apr-4 - **Comment**:
I've built a new vagrant image and this is part of it now. Thanks for the report. https://forge-allura.apache.org/p/allura/wiki/Install%20and%20Run%20Allura%20-%20Vagrant/ is updated to refer to the new vagrant box URL. --- ** [tickets:#7304] Vagrant instance needs /srv/git/p to be created ** **Status:** closed **Milestone:** forge-apr-4 **Created:** Tue Apr 01, 2014 11:10 PM UTC by Hugh Brown **Last Updated:** Wed Apr 02, 2014 03:04 PM UTC **Owner:** Dave Brondsema I've just downloaded and ran the [Vagrant instance](http://sourceforge.net/projects/allura/files/vagrant/allura-ubuntu-1204-server-amd64-20130807.box) following the instructions [here](https://forge-allura.apache.org/p/allura/wiki/Install%20and%20Run%20Allura%20-%20Vagrant/). I was able to log in and create a project; however, when I went to the git page (http://localhost:8080/p/project/code/), all I saw was a spinner (not sure what to call that, but I'm sure you know what I mean). This hadn't changed after 20 minutes or so. In the end, I destroyed the VM and recreated it. I was then able to get around the problem by running: sudo chown vagrant /srv mkdir -p /srv/git/p and then the usual "update_allura; ~/start_allura" commands. These steps are noted in the file "INSTALL.markdown", but a notice from the web interface about missing directories would be helpful; thus, I've marked the component as "SCM". However, I'd guess the Vagrant instance should come with this set up as well. Thanks for a great project, and please let me know if you need any further info. --- Sent from sourceforge.net because [email protected] is subscribed to https://sourceforge.net/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
