I completely forgot I made the _dots completion function do this in the first place. Past Dani did some really cool stuff! Anyway, the dot repos now live on Gitea, so the completion function needs to fetch the list from there instead. It's not difficult, the API is very simple.
|2 months ago|
|config/zsh/functions||2 months ago|
|local/bin||9 months ago|
|site||3 months ago|
|.gitignore||9 months ago|
|.stow-local-ignore||1 year ago|
|.stow-rename||5 years ago|
|README.md||1 year ago|
A fast and easy bootstrap for my dotfiles that also acts as a simple management script once installed. Bootstrapping is as simple as:
curl https://dots.00dani.me | zsh
If you're wary about piping scripts into your shell - you should be - then feel free to download the script and check it out first.
dots is designed to crash harmlessly rather than run something dangerous if
curl is interrupted, however.
curl https://dots.00dani.me > dots less dots # reviewing ... looks okay! zsh dots
By default, packages are installed by
~/dotfiles and then linked into
~ using Stow. Environment variables are available for customising this behaviour.
DOTFILES- the location to clone new packages. Defaults to
~/dotfiles. Don't set it to
~, because that'll just be super confusing.
DOTS_SOURCE_PREFIX- a URL prefix that will be prepended to simple package names, like "git" and "vim". Defaults to
https://git.00dani.me/dot. You might want to change this to point at your own Git hosting.
STOW- which GNU Stow binary to use. Defaults to
stow. You probably don't need to change this.
HOME- the target directory for linking packages. Probably not a good idea to change this either.
git and many other tools,
dots is based around subcommands for accessing particular functions. The available commands are:
Set up dotfiles on a brand-new system. Will create a
DOTFILES package directory, clone GNU Stow into it if necessary, clone itself and other default packages, and then link everything using Stow. This is the default command if
dots is run on a system where
DOTFILES doesn't already exist, leading to the succinct bootstrap snippet shown above.
Will clone one or more packages specified into your
DOTFILES directory. Packages must be specified as Git repository URLs, but two forms of shorthand are supported:
- GitHub package paths: "sharkdp/bat", "hlandau/acmetool". "https://github.com/" will automatically be prepended to find the correct GitHub repository.
- Simple package names: "git", "emacs", "task". The entire
DOTS_SOURCE_PREFIXis prepended to these names, hopefully producing a URL that points to your self-hosted Git service.
Will simply run
git fetch -p for each of the specified package names. If there are no package names provided, will implicitly run over all packages.
Will employ GNU Stow to symlink each of the packages specified by name into your
HOME. If no package names are provided, will implicitly link all packages.
Very similar to
fetch. Will simply run
git pull for each of the specified package names. If there are no package names provided, will implicitly run over all packages.
Can be abbreviated to
st. Will list all packages you have cloned into your dotfiles directory, along with their Git status (whether the working directory is clean, whether there are commits to push or pull, that sort of thing). This command is the default if you have already bootstrapped.