knex cli tool doesn't take --cwd option

[SohumB]

There's code to read it from argv.cwd, but you can't specify it - it goes error: unknown option --cwd. We kinda need it, because we don't want the working directory to change when we run knex.

[tkellen]

This is fixed in #327 but you can solve this problem now by using the --knexfile option, passing the full path to your knexfile.

[SohumB]

No, you can't, actually - if you specify a knexfile in a different
directory, it chdirs to that directory... for some reason.

Thanks for the fix!
On Jun 17, 2014 12:06 AM, "Tyler Kellen" notifications@github.com wrote:

This is fixed in #327 #327 but
you can solve this problem now by using the --knexfile option, passing
the full path to your knexfile.

—
Reply to this email directly or view it on GitHub
#326 (comment).

[tgriesser]

@tkellen what was the reason again for switching directories here?

Was it something that doesn't apply to the way that I'm probably improperly using liftoff here :)

[tkellen]

Liftoff has typically been used to handle configuration files for task runners. In that context, consumers usually want the process to chdir to the directory of the config, that way all file operations are performed relative to it. You might consider removing that from here:
https://github.com/tgriesser/knex/blob/master/lib/bin/cli.js#L152-L155

...but don't think I would. @SohumB, what is the use case that drives the need for the process to not chdir? It sounds like you should be invoking migrations programmatically rather than calling out to the CLI.

[SohumB]

The usecase is that we use a different set of config-munging libraries that step in before knex even sees the knexfile, and the path specified is relative to the cwd for them. You're probably right, we probably should be running this programmatically.

[tkellen]

Definitely sounds like a case for using the migration API.