matomo-org/matomo-dev-environment

Matomo Development Environment (Vagrant)

matomo-dev-environment's Issues

Repository not found

Hi, do i miss something or is there an alternative for the repository url? kind regards, Reinhard

Cloning into 'puppet/modules/apt'...
 fatal: remote error: 
   Repository not found.
 Clone of 'git://github.com/camptocamp/puppet-apt' into submodule path 'puppet/modules/apt' failed

Install developer documentation

It would be nice to have the developer documentation preinstalled so even when you are offline you can still access the documentation. Could be available under developer.piwik. Also allows you to easily contribute to this project. For more information see https://github.com/piwik/piwik-dev-environment/

Install redis tools

I think we already install redis by default but an outdated version via apt. Latest redis server version should be installed and configured to run as a daemon. We need at least Redis 2.8.0

phpredis extension should be installed.

Would be nice to have also https://github.com/ErikDubbelboer/phpRedisAdmin preinstalled under redis.piwik

Clone failing due to permissions problem

Hi there,

I'm getting the following error:

Cloning into 'puppet/modules/inifile'...
Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
fatal: clone of '[email protected]:puppetlabs/puppetlabs-inifile.git' into submodule path 'puppet/modules/inifile' failed

Install MailCatcher

MailCatcher runs a super simple SMTP server which catches any message sent to it to display in a web interface see http://mailcatcher.me/ It would be nice to have this preinstalled otherwise one has to set it up over and over again. Maybe even Piwik could be configured to use it automatically.

UI could be maybe available under mail.piwik

Puppet 4.1 is installed, breaking the provisioning

The current vagrant file installs a not backwards compatible puppet version (4.1 currently) while the configuration is for puppet 3.

For me the workaround was to prevent the installation of a custom puppet gem:

sed -s 's/sudo gem install puppet/#sudo gem install puppet' Vagrantfile
sed -s 's/sudo gem install hiera/#sudo gem install hiera' Vagrantfile
sed -s 's/sudo gem install hiera-puppet/#sudo gem install hiera-puppet' Vagrantfile

This works because the ubuntu cloudimage contains puppet and hiera.

Puppet-apt submodule repository is not found

Cloning this repo with --recursive flag fails with "Clone of 'git://github.com/camptocamp/puppet-apt' into submodule path 'puppet/modules/apt' failed".

Install Piwik issues mirror

This one is maybe rather interesting for core developers. It would be nice to have issues.piwik.org preinstalled on the development box under issues.piwik. Ideally there would be also a cronjob running syncing the issues every day or so with Github.

This way you cannot only easier contribute to this project but also you always have a local backup of all the issues in case you are offline and still want to work on issues.

More information: https://github.com/piwik/github-issues-mirror

Socket location not allowed with ubuntu cloud image

The socket for nginx/php5-fpm is currently targeted at

leads to a permission denied problem
from dmesg

[12519.666697] init: php5-fpm main process (12528) terminated with status 78
[12519.666706] init: php5-fpm main process ended, respawning
[12519.749501] init: php5-fpm main process (12536) terminated with status 78
[12519.749509] init: php5-fpm respawning too fast, stopped

When starting manually

[14-Jun-2015 14:24:26] ERROR: unable to bind listening socket for address '/home/vagrant/www/piwik/tmp/fpm.socket': Operation not permitted (1)
[14-Jun-2015 14:24:26] ERROR: FPM initialization failed

This is caused by restrictions where the socket can be created on ubuntu.

Suggested fix is to use /var/run for the socket
As a quick workaround:
In nginx.pp change

$socket_path = "${docroot}/tmp/fpm.socket"

to

$socket_path = "/var/run/piwik-fpm.socket"

Potential Misconfiguration

We are a group of researchers from Yale University building a tool to finding bugs in configurations files. To evaluate the effectiveness of our tool, we randomly selected 1000 open source configuration files to verify and are requesting feedback on our error report. Your file https://raw.githubusercontent.com/piwik/piwik-dev-environment/964df0d48ec23b7a9b5ca403daa30ea5a4f67026/puppet/files/etc/mysql/my.cnf was among those files. When we ran our tool your file, it reported the following potential errors.

[MISSING ERROR: Expected "key-buffer[isamchk]" in the same file as "[isamchk]"
In the training set we saw: True 69 times, False 1 times
]

The training set referenced in the report is taken from the industrial configuration files at https://github.com/tianyin/configuration_datasets. Note that even if your system is currently working, these bug may manifest itself only under large traffic loads or different system environments.

If you feel the any of above errors may indeed cause problems either on your system, or a different system, please comment on this issue report in the space below. This will help use to improve our tool. If you do not believe this is a potential bug, please feel free to close this issue. If possible we would appreciate your feedback before July 27.

If you would like find out more about how we detected these bug, you can find the open source tool at https://github.com/santolucito/ConfigV. For a quick overview of this tool, you can watch this video at https://youtu.be/plliEh-5MpM. If you have further questions, or would like to get involved with this project, feel free to reach out over email at [email protected].

Thank you for your time!

Error: Could not parse application options: invalid option: --manifestdir

When I executed the vagrant up command it ended with an error:

Error: Could not parse application options: invalid option: --manifestdir

How can I fix it?

Full log is here:

Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'trusty64' could not be found. Attempting to find and install...
    default: Box Provider: virtualbox
    default: Box Version: >= 0
==> default: Box file was not detected as metadata. Adding it directly...
==> default: Adding box 'trusty64' (v0) for provider: virtualbox
    default: Downloading: https://cloud-images.ubuntu.com/vagrant/trusty/current/trusty-server-cloudimg-amd64-vagrant-disk1
    default: Progress: 100% (Rate: 1170k/s, Estimated time remaining: --:--:--)
==> default: Successfully added box 'trusty64' (v0) for 'virtualbox'!
==> default: Importing base box 'trusty64'...
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: piwik-dev-environment_default_1438688840836_21904
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
    default: Adapter 2: hostonly
==> default: Forwarding ports...
    default: 22 => 2222 (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Warning: Connection timeout. Retrying...
    default:
    default: Vagrant insecure key detected. Vagrant will automatically replace
    default: this with a newly generated keypair for better security.
    default:
    default: Inserting generated public key within guest...
    default: Removing insecure key from the guest if it's present...
    default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
==> default: Setting hostname...
==> default: Configuring and enabling network interfaces...
==> default: Mounting shared folders...
    default: /vagrant => D:/Git/piwik-dev-environment
    default: /etc/puppet/files => D:/Git/piwik-dev-environment/puppet/files
    default: /home/vagrant/www => D:/Git/piwik-dev-environment/www
    default: /tmp/vagrant-puppet/modules-48bf73244a40076992a5cef90c07f471 => D:/Git/piwik-dev-environment/puppet/modules
    default: /tmp/vagrant-puppet/manifests-768747907b90c39ab6f16fcb3320897a => D:/Git/piwik-dev-environment/puppet
==> default: Running provisioner: shell...
    default: Running: inline script
==> default: stdin: is not a tty
==> default: Reading package lists...
==> default: Building dependency tree...
==> default: Reading state information...
==> default: ruby is already the newest version.
==> default: 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
==> default: Successfully installed facter-2.4.4
==> default: Successfully installed json_pure-1.8.2
==> default: Successfully installed hiera-3.0.1
==> default: Successfully installed puppet-4.2.1
==> default: 4 gems installed
==> default: Installing ri documentation for facter-2.4.4...
==> default: Installing ri documentation for json_pure-1.8.2...
==> default: Installing ri documentation for hiera-3.0.1...
==> default: Installing ri documentation for puppet-4.2.1...
==> default: Installing RDoc documentation for facter-2.4.4...
==> default: Installing RDoc documentation for json_pure-1.8.2...
==> default: Installing RDoc documentation for hiera-3.0.1...
==> default: Installing RDoc documentation for puppet-4.2.1...
==> default: Successfully installed hiera-3.0.1
==> default: 1 gem installed
==> default: Installing ri documentation for hiera-3.0.1...
==> default: Installing RDoc documentation for hiera-3.0.1...
==> default: Successfully installed hiera-1.3.4
==> default: Successfully installed hiera-puppet-1.0.0
==> default: 2 gems installed
==> default: Installing ri documentation for hiera-1.3.4...
==> default: Installing ri documentation for hiera-puppet-1.0.0...
==> default: Installing RDoc documentation for hiera-1.3.4...
==> default: Installing RDoc documentation for hiera-puppet-1.0.0...
==> default: Running provisioner: puppet...
==> default: Running Puppet with site.pp...
==> default: stdin: is not a tty
==> default: Error: Could not parse application options: invalid option: --manifestdir
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

Find a way to make it work with an existing Piwik install

I've been trying to use the Vagrant box with my Piwik install, but with no success until now.

piwik/
    # contains Piwik code
piwik-dev-environment/
    ...
    www/
        piwik/ # hey Piwik is cloned here again

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 and vagrant up on the Piwik repository.

composer run missing

The current provisioning does not include the required composer run to be able to use piwik. Either the documentation needs a fix or a composer run should be in place, f.e. instead of this comment

https://github.com/piwik/piwik-dev-environment/blob/master/puppet/modules/piwik/manifests/init.pp#L73

Docker building error: fast_gettext requires Ruby version >= 2.1.0.

After running command docker build -t piwikdev . I get:

---> 98928575c77e
Step 15/26 : RUN gem install puppet
 ---> Running in 4e5aeff1182f
ERROR:  Error installing puppet:
        fast_gettext requires Ruby version >= 2.1.0.
The command '/bin/sh -c gem install puppet' returned a non-zero code: 1

Install pimp my log

It is a log viewer see http://pimpmylog.com/

I am using it on my local instance for a while but when I destroy my vagrant box I'd have to reinstall again. Would be nice to have this preinstalled under logs.piwik.

This is also useful when running the tests on AWS to easily have a look at the logs afterwards.

Error building the VirtualBox: thor requires Ruby version >= 2.0.0

Running vagrant up fails with the following error:

==> default: Mounting shared folders...
    default: /vagrant => /home/renata-on2/Dev/matomo/matomo-dev-environment
    default: /etc/puppet/files => /home/renata-on2/Dev/matomo/matomo-dev-environment/puppet/files
    default: /home/vagrant/www => /home/renata-on2/Dev/matomo/matomo-dev-environment/www
    default: /tmp/vagrant-puppet/modules-9845a071be6f3196616349b4f72550fa => /home/renata-on2/Dev/matomo/matomo-dev-environment/puppet/modules
    default: /tmp/vagrant-puppet/manifests-768747907b90c39ab6f16fcb3320897a => /home/renata-on2/Dev/matomo/matomo-dev-environment/puppet
==> default: Running provisioner: shell...
    default: Running: inline script
    default: Reading package lists...
    default: Building dependency tree...
    default: Reading state information...
    default: ruby is already the newest version.
    default: 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
    default: ERROR:  Error installing puppet:
    default:    thor requires Ruby version >= 2.0.0.
    default: Successfully installed hiera-3.6.0
    default: 1 gem installed
    default: Installing ri documentation for hiera-3.6.0...
    default: Installing RDoc documentation for hiera-3.6.0...
    default: ERROR:  Error installing hiera-puppet:
    default:    json_pure requires Ruby version >= 2.0.
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.