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

Startup variables and parameters #212

Closed
Deathorn opened this issue Oct 23, 2016 · 3 comments
Closed

Startup variables and parameters #212

Deathorn opened this issue Oct 23, 2016 · 3 comments

Comments

@Deathorn
Copy link

@Deathorn Deathorn commented Oct 23, 2016

Hello. Am I missing something, but there is no support for environment variables like GNUPGHOME, PASSWORD_STORE_DIR, PASSWORD_STORE_KEY etc? Also there is no support for parameters to set things like GPG home and pass stuff and startup, right? Can we have it? :)

@annejan
Copy link
Member

@annejan annejan commented Oct 23, 2016

Currently PASSWORD_STORE_DIR is the only one that is used . .
But not in the way you might want, it's used for the 'profiles' in QtPass

I'm guessing you would like to have the environment variables to be passed to the internal QtPass environment for pass to use and for the fallback gpg2 . .
That sounds really do-able . .

Loading

@Deathorn
Copy link
Author

@Deathorn Deathorn commented Oct 23, 2016

Basically I want to have different launch scripts, where environment is set to use different places for GPG keys and home for pass. That is to make QtPass more "portable"-like and maybe run more than one instance of the app.

Loading

@annejan
Copy link
Member

@annejan annejan commented Oct 23, 2016

Currently there is a compile flag to disable the "single app" functionality -DSINGLE_APP=0
I'll look into honouring the external environment variables in the internal QProcess environment.

Loading

@annejan annejan closed this Aug 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants