gdk update fails with Geo secondary node
When running gdk update
on a GitLab secondary Geo node, it runs rake db:migrate
. But that fails because the database is in read-only mode.
We should detect if the database is in read-only mode, and skip db:migrate
if so.
Next to that, we should run geo:db:migrate
when the directory postgresql-geo
exists, because one might develop Geo secondary features on a primary node so you need to be able to run tests with the Geo tracking database.