Hi, we are now using the great CUBA platform from a few months, everything is going really good but we have two little questions that, even looking for a solution, has not a good answer so far.
how manage the project settings, like mysql localhost and other setting, when you have more than one developer working on a single project? I mean, every time a developer push the project to the version control, overwrites the previous values… so how to work with that?
in somehow linked to the first question, how we can manage the dev, qa, prod envs? We found a few threads speaking about it but not an “official” solution to this problem…
First of all, I have to ask, are you familiar with the IntelliJ IDEA’s concept of “VCS change lists”?
Personally in my practice when I alter contents of the file that I don’t want to commit back to version control, I create separate “dont commit” change list, put changed file to that list, and forget about the problem.
put all developer-machine-local properties to the new applocal.properties file. All developers in the team will need to create and fill that file manually, because this file will not come to VCS.
Spring profiles are the direct solution - you can define dev/qa/prod-specific Bean implementations or assign qa/prod-specific application property files.
OS environment variables can be used to pass secret variables (database credentials) to the application in qa / prod environments.