Merge independent repo of config files
[distro-setup] / README
1 ~2.7k lines of bash to setup all my computers
2
3 Initial os install is also automated using a separate repo called
4 automated-distro-installer, also at iankelling.org/git.
5
6 This is not meant for other people to run verbatum, but for them to read
7 and copy the good parts. It has dependencies on other repos at
8 https://iankelling.org/git. Most notably, my bashrc, distro functions,
9 and config files repo.
10
11
12 The main thing missing for someone else to use things is the expected
13 location of repos in the filesystem. So you would need to lookout for
14 paths starting with /a and adjust them.
15
16 Background: reasoning behind using /a: The home directory is typically
17 used for local software development, but I use paths like /a instead,
18 for the following reasons:
19
20 1. I want to run code directly from where I work on it, instead of
21 always having to create and use some install process. If that code is in
22 a home directory, and you want to run it as root (especially in contexts
23 where SUDO_USER is not set, like cron/systemd), you have to hardcode the
24 username for /home/username, or create some install process where that
25 username is saved somewhere, and then you are stuck with a single
26 username. If it ever got packaged for a gnu/linux distro, it would rely
27 on a hardcoded path with no username in it, so let's just do that.
28
29 2. The home directory is inconvenient. It's filled with a bunch of junk
30 you don't care about, which makes directory listing horrible, makes it so
31 you can't back it up easily (for example, gvfs mountpoint in it breaks
32 lots of things), and has things you don't want to backup. So, you could
33 use a subdirectory. But typing /s is much faster than ~/s and in every
34 root context, /home/username/s.
35
36
37 Part of how I run GNU/Linux. I try fully automate my systems and store
38 all configs and scripts, except private info at
39 https://iankelling.org/git.
40
41 Please email me if you have a patches, bugs, feedback, or republish this
42 somewhere else: Ian Kelling <ian@iankelling.org>.