You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+35-2Lines changed: 35 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -102,7 +102,7 @@ Do the following to upgrade your ~/.dotfiles safely:
102
102
2.`cd ~/.dotfiles`
103
103
3. update dotfiles: `git up` or `git pull`
104
104
4. remove old submodule location: `rm -rf .vim` (now lives in `homedir/.vim`)
105
-
5. inspect `install.sh` and `config.js` to make sure all the software you want is installed
105
+
5. inspect `install.sh` and the `software/` directory to make sure all the software you want is installed
106
106
6. inspect `homedir/*` for any changes you want to port from `./dotfiles_old`
107
107
7. run `install.sh` again
108
108
@@ -253,7 +253,40 @@ The following will only happen if you agree on the prompt
253
253
# Software Installation
254
254
255
255
homebrew, fontconfig, git, nvm (node + npm), and zsh (latest) are all installed inside the `install.sh` as foundational software for running this project.
256
-
Additional software is configured in `config.js` and can be customized in your own fork/branch (you can change everything in your own fork/brance).
256
+
257
+
Additional software is configured in separate files within the `software/` directory and can be customized in your own fork/branch:
258
+
259
+
-`software/brew.js` - Homebrew utilities and command-line tools
You can add additional Homebrew packages by creating a `.BrewFile` in the `homedir/` directory. This file should contain one package per line, with comments starting with `#`.
268
+
269
+
Example `.BrewFile`:
270
+
```
271
+
# Additional Homebrew packages
272
+
htop
273
+
neofetch
274
+
ripgrep
275
+
fd
276
+
exa
277
+
```
278
+
279
+
## Installation Prompts
280
+
281
+
When running the installation script, you'll be prompted for each software type:
282
+
283
+
1.**Homebrew utilities** - Command-line tools and utilities
284
+
2.**Homebrew desktop apps** - GUI applications
285
+
3.**NPM global packages** - Node.js packages installed globally
286
+
4.**Mac App Store apps** - Applications from the Mac App Store
287
+
5.**Ruby gems** - Ruby packages
288
+
289
+
Each prompt allows you to choose whether to install that category of software or skip it.
You can add additional Homebrew packages by creating a `.BrewFile` in the `homedir/` directory. This file should contain one package per line, with comments starting with `#`.
32
+
33
+
Example `.BrewFile`:
34
+
```
35
+
# Additional Homebrew packages
36
+
htop
37
+
neofetch
38
+
ripgrep
39
+
fd
40
+
exa
41
+
```
42
+
43
+
## Usage
44
+
45
+
When running the installation script, you'll be prompted for each software type:
46
+
47
+
1.**Homebrew utilities** - Command-line tools and utilities
48
+
2.**Homebrew desktop apps** - GUI applications
49
+
3.**NPM global packages** - Node.js packages installed globally
50
+
4.**Mac App Store apps** - Applications from the Mac App Store
51
+
5.**Ruby gems** - Ruby packages
52
+
53
+
Each prompt allows you to choose whether to install that category of software or skip it.
54
+
55
+
## Adding Packages
56
+
57
+
To add packages to any category, simply edit the corresponding `.js` file in this directory and add the package name to the `packages` array. The packages will be automatically installed when you run the installation script and choose to install that category.
58
+
59
+
## Adding New Software Types
60
+
61
+
To add a new software type:
62
+
63
+
1. Create a new `.js` file in this directory
64
+
2. Export an object with `name`, `type`, and `packages` properties
65
+
3. Add the filename to the `softwareFiles` array in `index.js`
66
+
4. Ensure the corresponding `require_*` function exists in `lib_sh/requirers.sh`
0 commit comments