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

[FEATURE] Allow baseConfigDir to be configurable #323

Closed
jgautsch opened this issue Aug 1, 2022 · 1 comment
Closed

[FEATURE] Allow baseConfigDir to be configurable #323

jgautsch opened this issue Aug 1, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@jgautsch
Copy link

jgautsch commented Aug 1, 2022

Is your feature request related to a problem? Please describe.

I'm trying to run doppler run in a docker container with USER nobody. However this fails with message Doppler Error: mkdir /nonexistent/.doppler: no such file or directory. This is due to baseConfigDir = utils.HomeDir() in config.go calling out to os.UserHomeDir() which for nobody is /nonexistent (which is not writable).

Describe the solution you'd like

A flag that lets me specify what baseConfigDir should be.

Describe alternatives you've considered

My options right now are to not use nobody, or to manually set $HOME so os.UserHomeDir() returns something I've prepared to be writable (this feels hacky).

Additional context

N/A

@jgautsch jgautsch added the enhancement New feature or request label Aug 1, 2022
@ryan-blunden
Copy link
Contributor

Hi @jgautsch,

If the base config directory needs to be explicitly set, I'd recommend the equivalent of what you're needing by setting the HOME env var inline:

HOME=/tmp doppler run -- start server

Would this be a sufficient workaround?

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Development

No branches or pull requests

3 participants