looking for suggestion: Managing Browser Config with Stow and Git in Dotfiles #6753
Unanswered
HiIamChaitanya
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Discussion: Managing Browser Config with Stow and Git in Dotfiles
Seeking suggestions on how to effectively manage browser configuration files within my dotfiles repository using stow and git.
I'm currently using `stow` to manage my dotfiles, which works well for most configurations. However, I'm encountering challenges specifically with browser configuration files.
My Goal:
To use `stow` for symbolic linking these configurations to their appropriate locations.
To maintain version control of these configurations using `git`.
Current Challenges:
I don’t really have a proper method to implement dotfiles config for the browser config.
Directly stowing these configurations might lead to clutter or potential conflicts with other dotfiles due to multiple profile options in Zen browser.
I'm looking for a clean and organized approach to manage these configurations, and only want a single profile that can be managed by dotfiles.
Specific Questions:
Are there recommended methods for managing browser configurations within a dotfiles repository?
How can I effectively use `stow` to manage symbolic links for browser profiles while maintaining separation?
Are there best practices for handling potentially sensitive data within browser configurations (e.g., excluding certain files from version control)?
Are there any alternative approaches that might be better suited for this task?
Looking forward to your insights and suggestions!
Beta Was this translation helpful? Give feedback.
All reactions