@mnapoli opened this Pull Request on August 11th 2015 Member

The piwik-dev-environment project is not maintained. Additionally it doesn't work with an existing Piwik install (https://github.com/piwik/piwik-dev-environment/issues/2) so I don't think it's worth fixing anyway.

I'm committing the Vagrant config I've been using (cleaned up of custom things). Using it is very simple:

  • set up the following aliases in /etc/hosts

    192.168.33.10   apache.piwik
    192.168.33.10   nginx.piwik
    192.168.33.10   phpmyadmin.piwik
  • run vagrant up
  • if Piwik is already installed, add apache.piwik to the trusted hosts: trusted_hosts[] = "apache.piwik"

That's it, Piwik is accessible at http://apache.piwik or http://nginx.piwik.

To run e.g. UI tests:

vagrant ssh
cd /vagrant
./console tests:run-ui

As you can see, the Piwik directory is synced in /vagrant (just like any other Vagrant setup, it's standard). The VM mounts the folder using NFS, which is much faster than the default vboxfs filesystem, however on OS X vagrant will ask for the root password to edit the NFS config (that's automatic, just type the root password when it tries to do something with sudo).

Feel free to merge it or not.

@tsteur commented on August 30th 2016 Owner

@mattab I'd suggest to close this PR. It's useful to have but we don't have anybody to maintain / support it. There is now https://github.com/piwik/docker-piwik which is supported and maintained so closing in favour of that.

@tsteur commented on August 30th 2016 Owner

@mattab feel free to reopen if needed

This Pull Request was closed on August 30th 2016
Powered by GitHub Issue Mirror