By default, MunkiReport uses its own embedded sqlite database, which apparently isn’t as robust as MySQL (the sqlite website has more information on sqlite’s appropriate uses and limitations). If you are extremely unfamiliar with MySQL databases, you may want to just stick with the default sqlite database until you are. I have a basic tutorial on how to set up MunkiReport with some sensible and relatively easy defaults.
I won’t go step by step with how to configure MySQL, because there are a lot of intricacies and when you move off the default sqlite to MySQL, you’ll likely have your own preferences for how you want to implement it.
That said, the following facts may help you if you are familiar with MySQL but aren’t as familiar with MunkiReport:
- This guide is handy for getting MySQL in general set up on macOS 10.12 (Sierra).
- You do have to manually create a MySQL user and MySQL database (MunkiReport will create the tables).
- Everything you need to configure MySQL is in the MunkiReport config.php file you copied from the original config_default.php. Simply uncomment the lines for MySQL and comment out the lines for sqlite.
- Assuming you are installing the MySQL database to the same server as MunkiReport, all the values should be good, except you may want to change the dbname (default is munkireport), the pdo_user (default munki), and the pdo_pass (default munki) to whatever the database, username, and password is for your MySQL database.
- You do actually have to still create the password hashes and usernames for MunkiReport admins and put them into the config.php file***. There is no user or user authentication table in the MySQL database.
- Even though you’ve copied and customized the config.php, deleting the original config_default.php file will break MunkiReport. Leave that file alone.
- While you can migrate your sqlite data to MySQL, there probably isn’t a need. Once your Munki clients check in on their own, the database will pretty much re-create itself.
*** Another alternative is to use LDAP or Active Directory authentication. You can find more details about that in the comments of the config_default.php file.