Add Vagrant config to run Piwik on Vagrant #8542
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The piwik-dev-environment project is not maintained. Additionally it doesn't work with an existing Piwik install (matomo-org/matomo-dev-environment#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
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:
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.