-
Notifications
You must be signed in to change notification settings - Fork 20
Find a way to make it work with an existing Piwik install #2
Comments
Maybe instead we could do something like Laravel (but much simpler):
That way we keep I'll have a look into that soon if nobody sees downsides with that (I badly need a VM). |
it sounds like a good idea. How much work would be involved in this? Also +1 if it help developers getting started with developing for Piwik. If so we want to explain how to use the vagrant thing in the Setting up developer guide here: http://developer.piwik.org/guides/getting-started-part-1#getting-setup-to-extend-piwik |
I honestly don't know how long it would take. |
The usual way this is handled is instead of cloning the code repo to www/piwik it would be NFS mounted into the vm (via sync folders). So the setup would be like @mnapoli already has it. e.g. https://github.com/TryGhost/Ghost-Vagrant/blob/master/Vagrantfile#L38 |
For people stumbling on this, see matomo-org/matomo#8542 |
I've been trying to use the Vagrant box with my Piwik install, but with no success until now.
I've tried symlinking
piwik-dev-environment/www/piwik
to the existing Piwik install but VirtualBox doesn't like that (since the simlinked repo is outside of the VM).How do you do it yourselves?
Should we consider merging that in Piwik's repo? I'd love (and I guess users too) to be able to do just
git clone
andvagrant up
on the Piwik repository.The text was updated successfully, but these errors were encountered: