Our Matomo instance has been running on virtual hosts for years. We’re now interested in deploying to containers in our AWS infrastructure. The docker hub image is a good addition, but can it be made “stateless” (i.e., not reliant on persistent storage) and still survive a restart? If so, how can the core:archive be run?
We’re experimenting with an additional container to do nothing but the archive, but are open to additional ideas (such as deployment from git). Thanks!
Did you have any luck finding information about this?
I am also wondering if it’s possible to use AWS Fargate and when needed run multiple instances of the container.
We’re working on this in Fargate now and I’ll post the solution when it’s complete. The archive can easily be done by using the web interface and a key. The largest issue is loss of the initial configuration when containers change state.
Hi @reynlds, do you have any updates on updating Matomo to be stateless/able to be run on Fargate? Keen to get this up and running.
This got put on the back burner with everything else taking priority. Looking to revisit this after first of the year.
Hey @reynlds, wanted to know if you had any update on this.
I’m trying to make the Tag Manager containers’ configuration persistent.
If you have an image or docker-compose example that would be very helpful.