Move things around

This commit is contained in:
Daniel Flanagan 2021-11-03 13:27:46 -05:00
parent 23c80e4a17
commit 5471969c79
Signed by: lytedev
GPG key ID: 5B2020A0F9921EF4

View file

@ -8,6 +8,22 @@ take what you like.
![Battlestation][battlestation-photo] ![Battlestation][battlestation-photo]
![Desktop Screenshot][desktop-screenshot] ![Desktop Screenshot][desktop-screenshot]
# Basic Setup
curl -Ss https://lyte.dev/df.sh | sh
## I don't like `curl ... | sh`
Clone the repo:
git clone https://git.lyte.dev/lytedev/dotfiles.git "$HOME/.config/lytedev-dotfiles"
Inspect and run the common (no macOS- or Linux-specific configuration) setup
`fish` script:
$EDITOR "$HOME/.config/lytedev-dotfiles/common/bin/dotfiles-setup"
"$HOME/.config/lytedev-dotfiles/common/bin/dotfiles-setup"
# Repo Structure # Repo Structure
My dotfiles are composed together by layering "environments" since I want my dotfiles to be flexible across servers, laptops, desktops, and even my phone (via Termux). My dotfiles are composed together by layering "environments" since I want my dotfiles to be flexible across servers, laptops, desktops, and even my phone (via Termux).
@ -52,23 +68,7 @@ configuration, so if you are setting up a Arch Linux desktop machine, you
cannot only link the `os/linux/arch` and `host/desktop` environments but will cannot only link the `os/linux/arch` and `host/desktop` environments but will
also need to include `os/linux` if you want the Linux-generic configuration. also need to include `os/linux` if you want the Linux-generic configuration.
# Basic Setup # Post-Setup
curl -Ss https://lyte.dev/df.sh | sh
## I don't like `curl ... | sh`
Clone the repo:
git clone https://git.lyte.dev/lytedev/dotfiles.git "$HOME/.config/lytedev-dotfiles"
Inspect and run the common (no macOS- or Linux-specific configuration) setup
`fish` script:
$EDITOR "$HOME/.config/lytedev-dotfiles/common/bin/dotfiles-setup"
"$HOME/.config/lytedev-dotfiles/common/bin/dotfiles-setup"
## Post-Setup
You will want to symlink relevant environment layers into the `$ENV_PATH` in You will want to symlink relevant environment layers into the `$ENV_PATH` in
order to have your OS-specific applications be configured and common order to have your OS-specific applications be configured and common