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

OXIDIZED_HOME being ignored #3255

Open
AvrumFeldman opened this issue Sep 4, 2024 · 1 comment
Open

OXIDIZED_HOME being ignored #3255

AvrumFeldman opened this issue Sep 4, 2024 · 1 comment
Assignees

Comments

@AvrumFeldman
Copy link

AvrumFeldman commented Sep 4, 2024

In oxidized v0.30.1 the OXIDIZED_HOME seems to be completely ignored.

When running the first time oxidized the base config file gets created in ~/.config/oxidized/config and on subsequent oxidized the errors show attempted loading of the default config file and not from the OXIDIZED_HOME path.

Even if I move the config file from ~/.config/oxidized/config to the $OXIDIZED_HOME path on subsequent oxidized the config file gets recreated at the default path of ~/.config/oxidized/config.

@robertcheramy robertcheramy self-assigned this Sep 5, 2024
robertcheramy added a commit that referenced this issue Sep 5, 2024
This bug was discovered while working on issue #3255
@robertcheramy
Copy link
Collaborator

I cannot reproduce. The error message did not use OXIDIZED_HOME, I fixed this in 26f48bd.

Are you sure OXIDZED_HOME is set? Try export | grep OXIDIZED_HOME before running oxidized.

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

No branches or pull requests

2 participants