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

Do not force config path to be relative to binary location #1

Closed
Roguelazer opened this issue Dec 15, 2016 · 1 comment
Closed

Do not force config path to be relative to binary location #1

Roguelazer opened this issue Dec 15, 2016 · 1 comment
Labels

Comments

@Roguelazer
Copy link

If I invoke aurora as follows:

/path/to/bin/aurora -c /etc/aurora.toml

I expect it to read the config from /etc/aurora.toml; however, it instead tries to read from /path/to/bin/etc/aurora.toml (that is to say, it always interprets the config path to be relative to the directory the executable is in).

@xuri xuri added the bug label Dec 18, 2016
xuri added a commit that referenced this issue Dec 18, 2016
- Bugfix Do not force config path to be relative to binary location (issue #1);
- Add `openpage` section to config file, if set `enabled = false` will not automatically open the browser (related issue #2);
- Sort tube names by alphabetically resolve issue #3;
@xuri
Copy link
Owner

xuri commented Dec 18, 2016

@Roguelazer Thanks for your issue. I have fix this bug and make a new release, please upgrade to the last version.

@xuri xuri closed this as completed Dec 18, 2016
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