Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

knex cli tool doesn't take --cwd option

See original GitHub issue

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.

Issue Analytics

State:
Created 9 years ago
Reactions:1
Comments:6 (6 by maintainers)

Top GitHub Comments

1reaction

SohumBcommented, Jun 16, 2014

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 https://github.com/tgriesser/knex/pull/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 https://github.com/tgriesser/knex/issues/326#issuecomment-46182170.

0reactions

tkellencommented, Jun 16, 2014

Definitely sounds like a case for using the migration API.