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

Environment variables support #97

Open
ilbertt opened this issue Jul 16, 2022 · 4 comments
Open

Environment variables support #97

ilbertt opened this issue Jul 16, 2022 · 4 comments

Comments

@ilbertt
Copy link

ilbertt commented Jul 16, 2022

I'd like to specify source and target connection parameters using an .env file or directly from shell, in order to integrate it in a CI/CD process I'm setting up. Is it supported?

@AnatolyFromPerion
Copy link
Contributor

Hello Luca,
A "usual" env vars aren't supported now, yet I think your request still can be fulfilled.
Mind following quotes from README.md:
As an option, you can move the entire config folder out of Nmig's directory and place it in any location
and
As an option, you can store the Nmig's logs in any location. All you need to do is to create the nmig_logs directory
then you can start Nmig via
$ npm start -- --conf-dir='/path/to/nmig_config' --logs-dir='/path/to/nmig_logs'

@ilbertt
Copy link
Author

ilbertt commented Jul 16, 2022

That's what I'm doing, using the inject-env package. I think it should be integrated in this repository, because it's common to have database connections as env variables and not hardcoded in the json.

@AnatolyFromPerion
Copy link
Contributor

So, as far as I understand, you aren't blocked for now, correct?

I can take it as a feature-request, yet I cannot promise a quick solution, since I'm a bit overwhelmed these days.

@ilbertt
Copy link
Author

ilbertt commented Jul 16, 2022

Seems nice! Thanks @AnatolyFromPerion

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

No branches or pull requests

2 participants