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.

Sign up for GitHub

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

Jump to bottom

Pass config.toml path as command-line argument #78

Closed
hug-dev opened this issue Dec 13, 2019 · 1 comment
Closed

Pass config.toml path as command-line argument #78

hug-dev opened this issue Dec 13, 2019 · 1 comment
Labels
enhancement New feature or request
Milestone
Parsec production...

Comments

@hug-dev
Copy link
Member

hug-dev commented Dec 13, 2019

Because of #69 we would need a way of launching Parsec with a different configuration file than the one on the same level where the command is executed.
A command line argument should be set to select the configuration path, defaulting to the one on the current directory if not present.
@hug-dev hug-dev added the enhancement New feature or request label Dec 13, 2019
@hug-dev hug-dev added this to the Parsec production ready milestone Dec 13, 2019
@hug-dev
Copy link
Member Author

hug-dev commented Jan 6, 2020

Closed by #81

@hug-dev hug-dev closed this as completed Jan 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
Parsec production ready
Development

No branches or pull requests
1 participant
@hug-dev