We just switched to using a MySQL backend and recently upgraded to 4.2. It’s been great!
However, we’d like to make future upgrades and redeploys as easy as possible. We have our settings and reports in MySQL, and our models in BitBucket. But when started the Looker service on a new server connected to the MySQL backend, it wasn’t quite ready to go. We still needed to re-point Looker to our models in BitBucket, which was accomplished by copying over the models directories. (This is also implied in the Creating Backups documentation.)
Instead, we’d love to see the new deployed Looker know all about the projects and their Git configuration. That way, it could clone the repos so that the models and user branches re-appear on the new server.
Is this configuration stored in MySQL somehow? Is there any post-processing step we can do to set this up? Or perhaps this could go into future release.
I love how easy it is to upgrade Looker, but being able to automatically transfer our models from git into the new server instance would be a huge help, too.