#Dotbot shell generator
#Dotbot shell windows

Then it examined the field_rules table line-by-line (starting from the top) to find a line in which the first column matched '.'.

#Dotbot shell generator

I myself put it in bin/install_dotfiles.sh.When my code generator wanted to generate code to assign a value to a field, the code generator constructed a string of the form '.', for example, Msg3.price. Where would the bash script go? Well it would be versioned within our dotfiles of course. I'm not a big fan of bash scripts, but their portability is pretty good, so I opted for making one of those. It would be good to get all our dotfiles ready ASAP on any Linux environment such that it would never feel like a chore.

Besides, worrying about all this also just wastes time.

bashrc of ours with some interesting stuff in it. Maybe this was actually an older Linux environment of ours which has an old. bashrc file already there that we might not want to just blindly override it with ours.

Our new Linux environment might come with some.

It's usually non-trivial for non-Linux-gurus recursively copy files from within a directory including files starting with a dot (most dotfiles we would like to version).

There are some issues with that again though that would be good to address: Now after that we would need to copy the files over from within the dotfiles directory to the home directory. We could call it dotfiles, and it could be within our home directory. So we'll need to clone into a new directory. Unfortunately in every Linux environment your home directory is not empty, and Git doesn't give you a way to clone into an existing directory. On any new Linux environment ideally we would like to clone our dotfiles into our home directory. Now that we have our dotfiles versioned in Git, we'll need to be able to clone it into new environments to make use of them. Whenever I want to add new file, I can just do git add -f to bypass the ignores. gitignore file in my home directory with this in it: *. If you started versioning your home directory, all the other unrelated files/directories would show up as unversioned, muddying up your git status output all the time. The dotfiles you would like to version is a very small subset of files/directories in your home directory There is a thing one might think as issues when considering to version files in your home directory. gitignore_global, bin/) for keeping them in sync than by using version control? dotfiles up and running on any server.įirst of all, what best way to save the state of several files (. Why do I opt for shell scripts in the title? That's so to minimize the amount of dependencies needed to be installed in order to get my. In this article, I'm going to show you what I did to solve this problem of mine. I have probably had to manually copy parts of local Linux configuration over and over again twenty times or so before I realized that this just has to be automated in some way so that I wouldn't have to suffer so much getting all my configuration ready any time I have to deal with a new Linux environment.

Then I installed Linux on a new computer and needed to find and copy my aliases again. Then on my personal DigitalOcean server I had another Linux environment, and I had to copy my configuration again.

#Dotbot shell windows

Then on my Windows on my Linux-like cygwin environment I had to copy that same. Then at home when I installed Ubuntu for the first time, I would have a. I had the one at my first workplace where I would have my own. Throughout my career I have been in many Linux environments.