Adding .my.cnf to disable column-statistics backup

[misilot]

Fixes #10176

The .my.cnf file is copied to /root/.my.cnf for each
Dockerfile that exists

Description

Adds a mysql configuration file that disables column-statistics for mysqldump, which allows the snipe-it backup to run as expected.

Fixes # 10176

Type of change

• Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Try running backup from existing container, to a mysql 5.x database server. It fails. Add the .my.cnf to /root with the following contents:

[mysqldump]
column-statistics=0

Run docker-compose exec snipe-it sh -c 'php artisan snipeit:backup', backup succeeds.

Checklist:

• I have read the Contributing documentation available here: https://snipe-it.readme.io/docs/contributing-overview
• I have formatted this PR according to the project guidelines: https://snipe-it.readme.io/docs/contributing-overview#pull-request-guidelines
• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[uberbrady]

Absolutely love it! Thank you.

[uberbrady]

@snipe should we try and merge this not only to develop, but to 'master' as well? I don't like the idea that some of our Docker users can't really back up effectively.

[misilot]

@uberbrady, do you want me to make a PR to master, or would you just prefer to chery-pick it into master afterwards?

[uberbrady]

Let's see what the boss says - but it's only one commit so I'm fine with cherrypicking.

[snipe]

This seems fine - if you want to open a PR against master as well, I'll take it.

[snipe]

(I am trying to get an RC out in the next day or so, so trying to limit changes as much as we can, but we already have a bunch of PRs to get through.)

[snipe]

Awesome, thanks!

[stefanp2021]

Hi!
Please excuse my question, can I already take advantage of this in my production environment?
Thanks a lot!
Best regards!
Stefan Pirker

[misilot]

Yes you could add this your existing running container. The easiest would probably to be to add it to your docker-compose.yml as a new volume mount point