Personal dotfiles saved and deployed using sadedot.

Go to file

Santiago Lo Coco 254005dc6b Update .dialogrc		2022-02-01 15:10:23 -03:00
dotfiles	Update .dialogrc	2022-02-01 15:10:23 -03:00
sadedot@0ea7ce1783	Update sadedot submodule	2022-02-01 15:02:15 -03:00
scripts	Change infobox message	2022-01-27 01:19:46 -03:00
.gitmodules	Add submodule	2022-01-19 14:25:44 -03:00
LICENSE.md	Add LICENSE.md	2022-01-19 15:13:16 -03:00
README.md	Update README.md	2022-01-19 23:28:58 -03:00

README.md

dotfiles

Personal dotfiles saved and deployed using sadedot.

Installation
Usage
Contributing
License

Installation

Fork this repository.

Usage

You have to move all your dotfiles to the dotfiles folder and then a sadedot script will do the symbolic links. Doing it this way, you can now upload them to your repository (to have a backup of them).

You should note that all these dotfiles (files or folders) will be symlinked in $HOME. So, if you want to symlink, for example, something in /etc, you have to put it in the dotfiles/other folder. Here you have to be careful as they will be installed in /. You can see an example here.

So, to run the script:

sh sadedot/scripts/bootstrap.sh

You can modify the sadedot/scripts/install.sh if you want to install some programs on your machine when this script is run. By default, sadedot/scripts/bootstrap.sh will not run this script, so you will need to use the -p flag if you want it to run sadedot/scripts/install.sh (it will run at the end of the script).

Updating

To keep your fork up to date with additions to the sadedot submodule, you must run:

sh sadedot/scripts/update.sh

Contributing

PRs are welcome.

License

MIT