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

Vaping config location considerations #98

Open
vegu opened this issue Sep 23, 2020 · 1 comment
Open

Vaping config location considerations #98

vegu opened this issue Sep 23, 2020 · 1 comment
Labels

Comments

@vegu
Copy link
Contributor

vegu commented Sep 23, 2020

Split out from #84 - discussion about relocating vaping config files and re-assessing the need for a vaping home directory per instance.

@bandtank wrote
I thought about this some more and it made me wonder why the path is to a directory instead of a file. Is there a reason you have to provide a directory? Would a config file not make more sense?

I think it would be simpler to make ~/.vaping automatically and then store all configuration files, log files, etc. in there. That would allow the user to use config files with different names instead of needing to name each config file the same way, but in different directories. A single, rotated log file that says which config file is being used would be really helpful.

@grizz grizz added the v2.0 label May 26, 2021
@oeggyknake
Copy link

oeggyknake commented Aug 30, 2021

When i see vape i was thinking like you sale e juice type items lol.

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

3 participants