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

influx cli: add option to specify path for configs file #17979

Closed
russorat opened this issue May 6, 2020 · 1 comment · Fixed by #19030
Closed

influx cli: add option to specify path for configs file #17979

russorat opened this issue May 6, 2020 · 1 comment · Fixed by #19030

Comments

@russorat
Copy link
Contributor

russorat commented May 6, 2020

from: #17813

I suggest adding a command-line option to influx setup that allows the user to specify the destination path for this file, so that it can be more easily integrated with existing container volume mounts.

@miken32
Copy link

miken32 commented May 8, 2020

This isn't just about Docker; in a traditional install, configuration files for a service should absolutely not be living in /home. I was able to move data files to /var/lib/ but I'm unable to start the server as a system user without a home directory. Looking forward to this feature being added so we can try 2.0 again.

jsteenb2 added a commit that referenced this issue Jul 22, 2020
jsteenb2 added a commit that referenced this issue Jul 23, 2020
introduces the new flag --configs-path to the influx CLI. This new
flag has a corresponding env var INFLUX_CONFIGS_PATH. It is useful
to export this env var in a shell dotfile for consumption throughout the
box.

closes: #17979
jsteenb2 added a commit that referenced this issue Jul 23, 2020
introduces the new flag --configs-path to the influx CLI. This new
flag has a corresponding env var INFLUX_CONFIGS_PATH. It is useful
to export this env var in a shell dotfile for consumption throughout the
box.

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

Successfully merging a pull request may close this issue.

2 participants