A couple of issues have come up when using Bolt in a project along with source control (Perforce, in this case).
1. Bolt demands to run the setup wizard on every computer that downloads the repository
This one isn't horrible but it is kind of annoying. The unit options database is present and everything appears to work, but Bolt still constantly pops up the "you should run the setup wizard!" window on any new computer. When pushing to source control, I made sure to get both the Assets and the Project Settings folders. Where is bolt storing its "I've been set up already" state on the first machine that it is somehow not coming through in the Perforce-downloaded copy? Or, is it expected that all users must generate the unit options database on their own machines?
2. Bolt then fails to run the setup wizard because it doesn't account for its files being read-only
A continuation of the first issue, this one is a bit more of a problem. Some version control software, like Perforce, has all files locked (marked read-only) by default, unless they are explicitly checked out. Bolt does not appear to check for or deal with this situation, as the setup wizard fails with an IO exception on the machine that downloaded the project through Perforce, because previously-created copies of the generated files came down with it, and were marked read-only. We had to go into Bolt's files and manually delete the file so that it could proceed.
Removing the read-only mark would also work, and is something that could be done in-code by Bolt automatically. Alternatively, if the expectation is that the unit options database and other Bolt-generated files are not supposed to be on version control, there should be some information in the documentation about that so we know not to include them (though IMO it's bad form to put anything within a Unity project's Assets folder that should be excluded from source control).
Customer support service by UserEcho