Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inconsistent usage documentation: conf/flyway.conf vs conf/flyway.properties vs ./flyway.conf #1382

Closed
sw00 opened this issue Jul 31, 2016 · 4 comments
Labels
Milestone

Comments

@sw00
Copy link
Contributor

sw00 commented Jul 31, 2016

I'm using flyway as a standalone CLI and found the information with regard to the default configFile option to be inconsistent and confusing. As I understand, flyway will look for a conf/flyway.properties only if invoked as a Maven plugin and not as a CLI.

$ flyway -h
Flyway 4.0.3 by Boxfuse

Usage
=====

flyway [options] command

By default, the configuration will be read from conf/flyway.conf.
Options passed from the command-line override the configuration.
configFile                   : Config file to use (default: conf/flyway.properties)
@axelfontaine
Copy link
Contributor

Flyway will look for config files in the order specified here: https://flywaydb.org/documentation/commandline/#configFile

Works as designed.

@sw00
Copy link
Contributor Author

sw00 commented Jul 31, 2016

Hi, thanks for looking at this.

In your link, I see no mention of a flyway.properties file - only flyway.conf.

If you could, please explain where a *.properties file is loaded from when using the CLI - I can find no line where this happens in org.flywaydb.commandline.Main.

@axelfontaine
Copy link
Contributor

Sorry I was a bit too quick here. Please see my comment on #1383

@axelfontaine axelfontaine reopened this Jul 31, 2016
@sw00
Copy link
Contributor Author

sw00 commented Jul 31, 2016

Great, thanks for the clarification. See #1383

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants