Activity overview
Latest activity by charonme
I'm using flyway commandline 10.11.0<br>
the different projects have their own repositories with their own sets of migrations in their own directories. Right now my workaround is to have separate config files for the separate projects and migrating them by calling flyway -configFiles=conf/proj1.toml -environment=local migrate<br>
from within the flyway directory (the drawbacks are that instead of being able to call flyway form anywhere I now have to be in the flyway directory to be able to reference the config file specific for each project and I have to write out an additional commandline parameter) / comments
I'm using flyway commandline 10.11.0<br>
the different projects have their own repositories with their own sets of migrations in their own directories. Right now my workaround is to have separate c...
yes, each project has its own set of migrations that only apply to the environments related to that project / comments
yes, each project has its own set of migrations that only apply to the environments related to that project
Is it possible to specify different sql locations for different environments in the config?
Is it possible to specify different sql locations for different
environments in the config? If not, what is the recommended way of using flyway with multiple different projects on the same machine?