6 ms·
Dotfiles feel too personal to share
- cipehr 1y agoI feel similarly. For me it’s less about my unique customizations and more about this paranoia of there being something remotely sensitive in my ssh configs or something… the idea of hostnames, ips, domains, etc “leaking” worries me. I use chezmoi to manage my dotfiles, if anyone has any advice on how to handle these worries I am all ears. I would love to share mine, even to just be able to point coworkers at my config.
- phailhaus 1y agoI get around that by sourcing a separate file in my config that I don't make public. Those are my company-specific settings.
- twp 1y agochezmoi includes secret scanning from https://gitleaks.io/ https://gitleaks.io/ by default to catch when you accidentally add a file with a secret in it. To be even more confident, you should add gitleaks as a git hook to your repo however.
- sureglymop 1y agoHow do you automatically set up the hooks, e.g. when you clone the repo on a new computer? Also, is there a way to automatically edit a chezmoi managed file in the chezmoi directory? I accidentally type stuff like "nvim .bashrc" way too often and then forget I never added the changes to chezmoi. It would be neat if there was a vim plugin or something that just opened the chezmoi file instead if it's managed.
- twp 1y agoPlease can you open an issue or discussion for these questions on https://github.com/twpayne/chezmoi https://github.com/twpayne/chezmoi - this way more people will both be able to help and more people will see the answer.
- sureglymop 1y agoI will do that. I apologize for raising it here in the first place and thank you for creating and maintaining a great piece of software!
- LeGrosDadai 1y agoIn chezmoi you can use gpg encryption: https://www.chezmoi.io/user-guide/encryption/ https://www.chezmoi.io/user-guide/encryption/
- athorax 1y agoI feel similarly. For me I know it is because of my rejection sensitive dysphoria. The fear of someone seeing and judging something personal of mine is quite uncomfortable. I don't have the same issue with code I write professionally.
- tasuki 1y ago> I don't have the same issue with code I write professionally. Why not?
- 8n4vidtmkvmk 1y agoCode I write professionally is polished before I send it for review. Code/dotfiles I write for myself are full of all kinds of heinous hacks.
- athorax 1y agoIt is less personal. I am writing code in the same style as the rest of the code base. Its more focused on correctness than my preferences. If someone critiques code in a PR I don't take it personally as it is usually in good faith.
- awill88 1y agoI feel similarly. There is virtually zero chance I’m going to clone and run someone else’s dotfiles. So the act of sharing them is a generous look into a developer’s toolchain and I’ve been inspired by others’ choices. So, if you know how, please share them!
- pavel_lishin 1y agoI've never straight up cloned them, but my dotfiles have grown in large part out of some copy-and-pastes from other people's.
- alexandroqc 1y agoI used to use chezmoi and had a great experience with it .It made it easy to choose exactly what I wanted to share. These days, I don’t have many devices, so I stopped using it. Still, it feels great when someone asks, “How did you set that up?” and I can instantly share my entire configuration through a GitHub repo.
- dayjah 1y agoI found the syncing process in chezmoi to be so hard to mentally model. I’d often change a file, forget that it was backed by the chezmoi store, later find myself trying to reconcile the differences, just so I could commit and share w/ another computer. nix + home-manager and snowfall lib, once over the multi month ramp up, have been such a breath of fresh air in multi system management
- zeppelin101 1y agoThis command solve the problem for me: https://www.chezmoi.io/reference/commands/merge-all/ https://www.chezmoi.io/reference/commands/merge-all/
- marcusb 1y agoI ended up writing some pretty hacky elisp to automatically load my chezmoi templates if I try to edit a Chezmoi-managed file. It'll also handle applying and pushing saved changes to my git remote so I don't forget that either. https://marcusb.org/posts/2025/01/frictionless-dotfile-management-with-chezmoi/#emacs https://marcusb.org/posts/2025/01/frictionless-dotfile-manag...
- pavel_lishin 1y agoI have two sets of dotfiles - public and private. I don't mind sharing my public ones - what do I care if someone on the internet thinks my tmux setup is non-optimal? But there are some things I do keep private, though they probably don't qualify as dotfiles, exactly - RSS subscription backups, some backup scripts that reveal filepaths I'd rather not have revealed, old outdated things like my znc, irssi, etc. configs...
- JoshTriplett 1y agoMy dotfiles have a massive .gitignore in them for all the things I don't want to share, or can't easily divide into shareable and non-shareable. The largest section in my .gitignore is: # Some transient, some configuration files, but configuration files get written # out every time, and not just the changed values. Some also contain # machine-specific configuration, and private data. It includes things like .config/libreoffice , which is a baffling combination of: - backup copies of documents (which should go elsewhere) - copies of icons from the icon theme (which should go elsewhere) - log files (which should go elsewhere) - piles of binary pack files, probably containing a mix of things - configuration in XML form (potentially useful to version), but with embedded lists of recently opened files (private, should go elsewhere), including base64-encoded thumbnails.
- deleted 1y ago[deleted]
- incognito124 1y agoI truly appreciate people sharing their dotfiles, I learned so much about vim and zsh just by reading other people's configuration alone (and the occasional comments there). Also, the quality of life improvements like `alias ..='cd ..'`, or mapping `l` such that it either opens a pager or lists a dir, depending on the argument. I'd never come up with those, and they're beyond useful.
- deleted 1y ago[deleted]
- jrm4 1y agoRIGHT? I could MAYBE see it if you were sharing your things on your personal blog -- but "github dotfile repos" feels wildly icky to me.
- apwell23 1y agowhy? no one cares about your dotfiles 99% of time.
- 8n4vidtmkvmk 1y agoI put all kinds of weird stuff in mine. Where/who I stole the alias from. Maybe some swear words. Broken stuff. Jokey stuff. I don't want people judging me. It's like publishing the worst of your sketch book or something. People just don't need to see it. Which really annoys me that everything is effectively public at my place of employment. I have to mildly censor myself all the time.
- sodapopcan 1y agoHow? What? It's not icky.
- jrm4 1y agoI mean, that's subjective. Kinda feels like uploading a picture of my bathroom/medicine cabinet. There's nothing in there particularly incriminating or whatever. Just kinda feels weird.
- fishbacon 1y agoI share my .emacs with people who ask. Not really for privacy, but because I would feel bad: If someone tried to use any of it and was not able to ask me what I was thinking. The usual answer is that I was not and we should change it. I would also have to distribute a couple of novel go programs that I am not proud of if I was sharing it publicly.
- qiine 1y agoI was close to upload my full dotfile dir to github, telling myself it would be handy when I switch computers.. Then I realized that some of those config files reflected a lot about my systems and personal preferences... and it was only going to be ever more detailed, so I said NOPE making separate repos for my nvim config maybe and that will be it! sorry.
- tracker1 1y agoYou can always use a private repository for it. And, yeah, it's been very useful. I pushed a relatively straight forward config for Windows and WSL a few years ago, I really need to update it. I also want to get my Linux config done as well. I mostly backup and restore from my NAS for my dot-files, and some of my ~/.config, though I need to nail that down a bit better, as ~/.config feels excessively bloated from a few apps.
- nobleach 1y agoMy dots are open to anyone who cares to view my GitHub. I do tend to keep employer specific aliases/stuff in an `.employer.zsh` file that is sourced by my main `.zshrc`. But my NeoVim config is completely open for inspection. I'm not doing anything all that extraordinary though. I don't share my dots on Reddit simply because I don't feel like using my real identity on that platform. When it comes to consuming the dots of others, I just switched to AxOS for Linux... and am auditioning Celestia (https://github.com/caelestia-dots/shell https://github.com/caelestia-dots/shell). This means that in 3 months, my desktop will likely look like everyone else's. I probably won't even commit any of this as it's not really my stuff.
- trostaft 1y agoThanks for the reference, that looks incredible.
- Insanity 1y agoThat actually looks pretty cool. Might have to play around a bit with Caelestia as well.
- petepete 1y agoSimilarly, I have two sets of dotfiles, a public one and a private one (hosted on my own server). Somehow, 11 people have starred my public ones on GitHub.
- tylergetsay 1y agoI feel the same about my NixOS config despite the "open repo" model kind of being a default in that ecosystem
- dayjah 1y agoOh man… that “how normal is this thing of mine” feeling writing nix gives me is such a weird characteristic of the ecosystem. I simultaneously don’t want anyone to see mine while desperately seeking affirmation that mine is not weird ^_^ Happy to hear I’m not alone!
- tylergetsay 1y agoIt makes me feel bad because I frequently will search github with "language:nix" to find usages, which is usually done in someones (sometimes the nixpkgs commit authors) personal config :')
- tootie 1y agoOne trick I use is putting secrets in 1password and just including the 1password URLs in my checked in my sample dotfile.
- err4nt 1y agoI think the key is that dotfiles are a different genre of (code) writing than production code, with different investment, different motivations, different pain points and histories, and a sensitivity to the author that's not required when analyzing production code. You're looking into someone's daily writings, not their polished releases. I think the fear is scrutiny, rejection, mockery for something that clearly works for you and you don't ever expect anyone else to use. But also partly that it's exposure without much reward in return. All these feelings are normal and it's fine to share or not share them. Just please honour the authors of the dotfiles you read even if you wouldn't ever think to use code in the way they do!
- QuercusMax 1y agoI'm sure I have stupid and weird stuff in my dotfiles. At one point I had bash set up so if I typed something like "gi tlog" it would fix it for me; this is obviously not something that everybody needs because it's due to my idiosyncratic typing-too-fast. I've been using Unix systems since last century; my standard way to do a find-and-replace in a file is still 'perl -pi -e s/foo/bar/ filename.txt'; I've been writing that for 25 years and I'm unlike to stop any time soon unless perl stops working. I'm sure there's a better way to do this, but :shrug:?
- jrockway 1y agoI've never felt that icky. I don't really have any secrets in my dotfiles, though I have in the past. In that case, I just encrypt the private stuff using my SSH private key (stored in 1password) and age (via sops-nix).
- seethishat 1y agoThey are private. Many people store env secrets (db conn strings, etc.) in .bashrc. It's meant to be a private place in your home folder for private things.
- k_roy 1y agoThey are really only private if you design it that way. There are numerous ways you could have access to those private parts of your bashrc, but still make the actual bashrc public. That's coming from my kubernetes background though, and handling secrets this way is not something that people are always accustomed to.
- nativeit 1y agoAren’t the default permissions 644?
- kernc 1y agoToo personal to share, but maybe too personal and important to share even with the members of the cloudy cartel, i.e. the Providers. Is exactly why I wrote myba that does full contents and paths encryption before syncing with the lapsable remotes ... https://kernc.github.io/myba/ https://kernc.github.io/myba/ Some things are better public. Some are not ...
- tecleandor 1y agoThat looks nice! The moment I started syncing dotfiles between my work and personal computers, I know it was an error because very different reasons. Difficulty of maintaining different OS details (Linux vs MacOS). What if leaked a private key or a sensible path. What if a pushed to the wrong place or somebody made public the wrong repository... When reading your comment something and idea came to mind about using something like sops to encrypt paths, passwords and keys. But I'll check yours first, so to avoid to construct a bunch of stuff that you've already done :D
- stopcoffee77 1y agoI am trying to contextualize git-based dotfiles. $ context set universe://work/customer-a/devops --update-dotfiles will "render" and apply one set of dotfiles $ context set unvierse://work/customer-b --update-dotfiles another set $ canvas dot apply user.name@remote.id:workspace-foo Will apply all dotfiles of a workspace-foo (git clone repo, symlink) $ canvas dot apply user.name@remote.id:workspace-bar/shell/bashrc will apply dotfiles of workspace-bar/shell/bashrc yes, complicated, probably hard to comprehend/reason about, work in progress
- thewisenerd 1y agothis reminds me of public repos of pass [1] i've seen in the wild same issue of intimacy, the paths aren't encrypted. [1] https://www.passwordstore.org/ https://www.passwordstore.org/
- stopcoffee77 1y ago[dead]
- twp 1y agoIt's not a question of share everything or share nothing - with https://chezmoi.io https://chezmoi.io you can choose exactly what you want to share: * You can keep your entire dotfile repo secret by using any private git hosting, including your own git hosting or a private GitHub repo. * You can keep individual files secret by using age or gpg encryption. If you repo is public, this only reveals the existence of the file, not its contents. * You can keep individual parts of your dotfiles secrets, e.g. API keys, by encrypting them or storing them in your password manager. All popular password managers are supported. Disclaimer: I'm the author of chezmoi.
- tecleandor 1y agoI used chezmoi briefly yeeeeeears ago, and I think it didn't have the 'encrypt only parts of the files' feature yet. I might test it again :)
- kjuulh 1y agoChezmoi has been a blessing to use. It is one of the only tools I've used that had been able to survive me neclecting it for months and then getting back to it. I'd love a more interactive diff when my dotfiles have driften too much. But otherwise it is perfect for my needs.
- twp 1y agohttps://www.chezmoi.io/reference/commands/merge-all/ https://www.chezmoi.io/reference/commands/merge-all/ might help you here - it opens your preferred merge tool for the dotfiles that have drifted.
- burnt-resistor 1y agoMeta had an internal tool called "dotsync". It persisted multiple revisions of dotfiles across multiple machines associated with a particular user's account. It supported ignoring history and secret files by patterns. This is a superset of simply storing all dotfiles in a single git repo. This unmaintained project seems suspiciously similar including the name: https://dotsync.org https://dotsync.org
- alisonatwork 1y agoThe first UNIX account I ever got was on a BSD, and the first thing I saw in the first file I learned how to open was: # A righteous umask umask 22 I'll never forget those lines because they seemed so mysterious and cool. And they informed my philosophy on how the internet should be. People should be able to see other people's stuff by default. It's nice for us to be able to learn from one another. It's harder to rely on the honor system for privacy nowadays, but I still think "share by default" is a noble ideal. That said, I also am unsure how best to overlap aliases and configs that are sensitive to my workplace with my everywhere config. Maybe I should have a .employer file that I source if it's there, but something about including that into my everywhere config feels decidedly not righteous.
- r3trohack3r 1y agoNot just the internet but communities too. High trust societies are great to live in, digitally and physically. Leave the doors unlocked, leave keys in the ignition, leave valuables on the table when you walk away. But high trust societies only work when the price of ongoing admission is not violating that trust. When you accept/tolerate/expect the violation of trust the doors lock.
- lcnPylGDnU4H9OF 1y ago> leave valuables on the table when you walk away I actually do this somewhat frequently at my local game shop. Thousands of dollars' worth of Magic: The Gathering cards (because I bring multiple decks instead of just the one I'm playing) in my backpack left behind as I go to get some water or something. > high trust societies only work when the price of ongoing admission is not violating that trust Indeed, the reason I feel comfortable doing that is I know that nobody wants to be banned from going to that store (and they would be). In this context, the community is small enough that rumors would likely circulate at other local shops and they might also become a bit of a pariah at those other places they could play.
- moi2388 1y agoVery true. It also helps that from my experience MTG players are some of the nicest people you’ll meet
- Cu3PO42 1y agoMy dotfiles are public [0], but getting there was work. I went through everyhing to make sure I don't accidentally leak something, all secrets are managed separately, you don't accidentally distribute something violating its licence, etc. I also feel the need to write docs for some things, that I never would if they were private (I haven't actually done that, I just feel that I should). I get everyone who wants to keep them private, but I'm also thankful for everyone who made them public so others can learn from them. [0] github.com/Cu3PO42/gleaming-glacier/tree/next
- gchamonlive 1y agoYou just have to put some effort into separating your dotfiles into a generic layer and a customization layer. Done something like this with my dotfiles repo, which now triples as a generic archlinux customisation tutorial with hyprland and a description of the backup strategy that is tightly coupled with the configuration layout: https://github.com/gchamon/archlinux-system-config https://github.com/gchamon/archlinux-system-config
- Insanity 1y agoI actually resonate with this as well, but similarly can't really explain why. I have my own set of dotfiles (one set for my 'home setup' and one set for my 'work setup'). They are versioned and stored on GitHub, and are actually relatively static at this point. And even though it's pretty standard stuff, I wouldn't feel comfortable sharing them publicly. Odd.
- luckydata 1y agois there some sort of utility to automatically backup and retrieve dotfiles from github to keep different computers synchronized?
- olddustytrail 1y agoWell, there is cron and git. I don't see why you need anything else.
- dcchambers 1y agoI split mine. I have public dotfiles and private. No need to share everything.
- deleted 1y ago[deleted]
- holman 1y agoI have like 7500 stars on my dotfiles over the last 15 years or so; it's definitely weird. It's kind of a different open source project entirely; the goal isn't really to make good software... it's to make good software for me. Most of the time in open source those overlap completely, but with dotfiles I'll get pulls that make sense, that can be helpful, but... at the end of the day they're my dotfiles and I don't really make large changes to them anymore. It's just a lot different from my other projects I manage. That said, mine also started before things like Oh My Zsh popped up, which are better frameworks to share and collaborate on these things. I think frameworks like that are great, and I think seeing someone's more "intimate" dotfiles is helpful, too- you get a look at how someone sets up their environment, which tends to be private unless you're doing a lot of pair programming. So yeah, just interesting all around.
- zahlman 1y agoSometimes there are valid security reasons for this, after all. (Looking at you, .pypirc .)
- CMCDragonkai 1y agoI've been keeping my personal .dotfiles publically for the past decade. https://github.com/cmcdragonkai/.dotfiles-nixos https://github.com/cmcdragonkai/.dotfiles-nixos. But I do agree that secrets need to be handled carefully. Look at my list of `.gitignore`! But (I'm biased of course) I would recommend using Polykey to manage your secrets instead leaving any trace of things on disk.
- justonceokay 1y agoInstalling a (read: many) custom vim plugins and color scheme and screen version and etc… stops being fun about the third time you have to log into a nameless server. That being said, there are some settings that I absolutely cannot live without; `j=gj` being a good example in vim. IMO your dot files are only useful to share if they are usable with the default software of the place you’ve shared them to. Otherwise they become a prison that forces you to install all your special versions and plugins and scripts and etc. on the other hand, I felt like making my dotfiles easy to share forced me to use as many default settings as possible, which in the long run saves me a lot of time and energy. “The only zen you’ll find on a mountain top is the zen you brought with you” is one of my favorite sayings, and in a weird way I find it fitting here. If you learn to love the default settings then every server feels like home.
- Ezhik 1y agoI honestly just can't vibe with the "don't customize because you'll log into other servers" thing. To me it feels like getting told to not put nice shelves in my home because other buildings don't have them.
- justonceokay 1y agoIt completely depends on your work environment. My experience has been doing a lot of admin work and working with distributed databases. I probably spend a third of my day in servers that are not mine. So for me it just doesn’t make sense to make a lot of configuration changes, especially changes that will end up in my muscle memory. Now my personal computer does have much nicer color schemes and a few plugins for code dev that I don’t carry around. But even then I try to use the defaults in my IDEs and browsers, because at this point I’m on work computer number.. 11? Configuring it is starting to get old
- treve 1y agoSeems like a great opportunity to learn a bit about automating this set up. Really not hard to upload a .vim directory on a remote server for example.
- alkh 1y agoThat's something I was a little bit conflicted about for some time. After using a few open source tools(shoutout to syncthing and linkding :)) and I realised that if you want to use something for free, sharing is the least you can do. My dotfiles are private for now cause I need to clean some commits(I think I might have added some private info before) but I intend to publish them eventually
- gknoy 1y ago> My dotfiles are private for now cause I need to clean some commits I had to do similar. I ended up deleting the git history and just recreating it before pushing. The best thing was to add a dependency on `~/.secrets` or other similar un-tracked file, which is basically just a source-able script that defines things like API keys, private URLs, etc.
- alkh 1y agoI thought about recreating the repo from scratch too. I was transfering from Intel to ARM Mac and keep a few tags/commits related to previous configs, so it is hard to just let it go :)
- superzamp 1y agoI think it's even realistic to say that dotfiles are vulnerable to being used as a fingerprint mechanism by nefarious packages. One could easily create an inventory of github profiles <> dotfiles; then read local dotfiles when their package gets installed on a developer laptop.
- meribold 1y agoSuch a nefarious package could also read browser cookies, SSH keys, emails, photos, and a million of other things.
- paffdragon 1y agoI once set out to share dotfiles as I set up a new workstation, but later removed the public repo. I realized I am often careless with that stuff, since it only lives on my machine and I am not managing them as public content, nor I want that extra overhead.
- lrvick 1y agoProfessional security researcher here. I would strongly discourage threat modeling with vibes. Your post already reveals potentially the scariest things someone might learn if you published your dotfiles: that you use Homebrew, pip, etc as part of them. In doing so you are telling everyone you allow any internet rando to have remote code execution rights on your computer. To me that is like boldly saying you like privacy in the same breath as saying you never lock your front door or close your drapes. Those package managers operate like Wikipedia where anyone can push whatever they want without signatures or vetting from poorly secured accounts without phishing-resistant 2FA etc. At that point you already allow anyone capable of creating a few useful PRs to Homebrew, basic phishing, or sim swapping the ability to see and publish anything on your computer, so your dotfiles being public should be the least of your concerns. Now you are probably thinking "There is no way tools that every smart person I know uses could be that wildly insecure" Ask yourself if those same people have experience exposing and exploiting supply chain attacks. We all have blind spots, and almost everyone has a massive blind spot here and my team and I have exploited it many times in audits. All said though, I personally publish my dotfiles because I am confident they are of more use to me and others public, and do not reveal anything useful to someone targeting me other than that I use some kind of Linux distro and neovim. Any sensitive work I do is in offline stateless virtual machines deterministically built from a supply chain with high accountability and I do not use any dotfiles in those environments. With good separation of concerns between yolo systems and hardened trusted systems, publishing information about either is perfectly fine. Almost no one has that kind of workflow separation though, usually accessing prod from their compromised dev macbooks.
- diarrhea 1y agoThis is extremely alarmist. If you are on Mac, developing anything at all with Python, those are going to be your tools. If you randomly guessed at developer setups, that is going to be one of the most common setups as well. What's next, I use a computer so someone could just upload a virus somewhere in hopes I happen upon it, which would be dangerous? I have dotfiles which not only specify Python, but also its version and some packages. That protects against typosquatting! I will never type those package names out manually again. And this is all in Nix (btw), so all hash-pinned!
- sodapopcan 1y agoI'll never understand people not wanting to share their dots. Obviously you have to have a way to not share the private stuff of which there are many simple solutions, but I've learned so much from reading other peoples. To each their own, of course.
- mystifyingpoi 1y agoI don't even know what the author means here. I put them public on GitHub, because I can clone them from anywhere and have my config on any machine. The approximate number of people, who read them and see what I did, is 0. I just "share" them for public and free backup. Someone thinking that bash aliases can be "intimate" is a next level of nerdyness for me. Reminds me of "gay code" scene from Silicon Valley.
- deleted 1y ago[deleted]
- vkaku 1y agoI keep my DotFiles on my GitHub not without its embarrassments, this will help me backup and restore my tools and workflows on systems anywhere I want it to. https://github.com/guilt/DotFiles https://github.com/guilt/DotFiles There's no knowledge shared here, just my own setup which can be barebones git cloned. Planning to add a curlbash installer here to help me set it up with a oneliner.
- jacobsenscott 1y agoIt takes a lot of discipline to keep secretes out of dotfiles. You should do that anyway, even if you have a private dotfile repo. Even if they aren't secrets per se - they can still be useful for social engineering. I don't understand why people think their configs are so special it is worth the risk.
- saagarjha 1y agoI keep mine public but sensitive data goes into another, private GitHub repo.
- wlindley 1y ago"...whenever 'a software' doesn't...." Ugh. "A software package" or "a piece of software" or perhaps "a program" but you don't have "one software" any more than you can have "one hardware" or "one information." Grammar, please!
- hk1337 1y agoI am more concerned about sharing something that someone can use to get access to my things that I keep locked away. I still have it public but I try and think about what I am pushing before I push.
- cyrialize 1y agoI get this feeling. I have a setup with my Emacs configuration that uses a file that is meant to live locally only, since I feel the contents of it feel too personal to share. (These are mainly Org-mode settings for specific file names and directories). https://github.com/cyrialize/.emacs.d/blob/main/private-template.el https://github.com/cyrialize/.emacs.d/blob/main/private-temp...
- profunctor 1y agoThis article feels like it’s about what and how this person stores their dotfiles and then has two lines about them feeling too personal to share. I’m surprised it’s so highly voted since it’s basically “I use stow”. Must be due to the interesting title.
- wulfstan 1y agoI would like to say an enormous thank you to Dave, who after a huge amount of pestering (and probably to try to save himself from further pestering) shared his .emacs filetree with me and told me to learn Lisp. Be generous with your dotfiles, and especially with the young and curious engineers who ask lots of questions about your setup. Pay it forward.
- burnt-resistor 1y agoSigh. 3 buckets: - Secrets and environment specifics <- these needs secure storage and don't get shared obviously - Local configuration overrides <- these need to be backed-up somehow and probably aren't useful for sharing either - Generic configuration <- these are the type of dotfiles that can be shared