![]() With my favourite text editor I create a file named and add these contents. conf that comes with the container, adding the GZIP detail and a logfile change. conf file, which is slightly updated from the default. I am going to stage Nginx in its own data directory, so first I create it. Adding Nginx-alpine to the compose file.My VPS image is Ubuntu 18.04, with Caddy 2, and the Docker Compose environment is set up as per this great Digital Ocean article.įor many of these config files, I will base them on the Matomo Docker example files on Github.įirst up it's a backup - in my case a Lightsail server snapshot. Now that I have eyeballed this list, I also realise I can reduce that memory-hungry 96MB Matomo database footprint by following my own process, so I will go eat my own dog food while I am at it. When invoking the Matomo console, that 52MB blows out which is the problem bringing me here. My biggest consumers are this blog (with embedded DB) at 87MB, the Matomo database at 91MB, and Matomo itself with 52MB. So it's ok, but any memory spike can blow it. Running a few screens and giving it some work to do can easily go over 600MB. That might seem like a lot for one small VPS, however in normal operation it runs at around 500MB usage. The Matomo stack including database is here, coexisting with this very Ghost blog, the Commento system that adorns this site, also with a database, and another small HTML/PHP site. I have a $5 AWS Lightsail image with 1GB memory. I will add a complete docker-compose.yml file at the end of the post. I am running a small VPS with 1GB memory, coexisting with other apps, so probably by upgrading to a 2GB version it would also solve this problem, but I'm all for efficiency, and making my life difficult! So my mission - replace the Matomo-apache container with Matomo-fpm and Nginx containers. Were I to take the FPM option, it requires an external web server. ![]() At the time of setup, I chose the Apache combo version for simplicity, as the web server is encapsulated in the container. Matomo make available Apache based and FPM (FastCGI Process Manager) based containers. The Matomo agents dutifully gather data from my web sites with the injected analytics code with no significant performance impact, however, when accessing the Matomo console, the VPS memory usage spikes, and kills the server. Some time ago I set up self-hosted Matomo in a Docker environment as a replacement for Google Analytics, mainly for privacy reasons. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |