Geo: Add a rake task that runs regular and/or tracking database migrations, which ever is applicable in the current context
The following discussion from !901 (merged) should be addressed:
-
@toon started a discussion: (+1 comment) I'd like to make this more generic. It would be cool if
rake
would figure out itself on which databases it should run migrations on. But so far I couldn't come up with something (that does not require multiple runs ofrake
, which would make it slow).Ideally this will not be Geo-specific, but generic to all users.
Let me think on it a little bit more...
If we had this, it would simplify GDK Makefile targets while avoiding running rake
multiple times (a waste of time).
Edited by Michael Kozono