dotfiles-sync
dotfiles-sync is a command line application which helps manage configuration files (typically dotfiles) across different machines and operating systems.
Motivation
I needed a solution which would allowed me to easily automate synchronising my configuration files as I jump between different machines which could be either Windows or Linux.
Getting Started
This package is deployed to pypi:
python -m pip install dotfiles-sync
The --help will always show the most up to date options:
❯ dotfiles --help
usage: dotfiles [-h] [-c CONFIG] [-w CONFIG_DIR] [-d] [-i] [-f FILTER [FILTER ...]] [--version] {list,sync,update} ...
positional arguments:
{list,sync,update}
optional arguments:
-h, --help show this help message and exit
-c CONFIG, --config CONFIG
dotfiles configuration. Points to target locations.
-w CONFIG_DIR, --config_dir CONFIG_DIR
Location of the configuration files to sync
-d, --dry Only read and show me what you would have done
-i, --interactive Before doing a write, ask for confirmation
-f FILTER [FILTER ...], --filter FILTER [FILTER ...]
keys(s) of the configuration to apply. If not set then apply them all
--version show program's version number and exit
This application relies on the fact that you store your configuration in source control and that you define a configuration file which declares your configurations you want to track along with paths per operating system.
An example of a configuration file is:
{
"config":
{
".bashrc":
{
"linux": "~/.bashrc",
"windows": "~/.bashrc"
}
}
}
Typically named dotfiles-sync.json, this file defines each of the configurations we are interested in along with the locations where they should live per operating system. In this example we have a single entry .bashrc which states that we have a file in the root of the configuration directory with the same name. The configuration directory is the directory where the central authority of that files live (typically a git repository which contains all your configuration files).
This entry can also be a folder or file within a subdirectory (e.g bash/.bashrc) for if you wanted to keep all your bash related configuration files organised into a bash folder in your repo.
Each entry contains paths to operating system specific path the file should be syncronised into. The operating systems supported here are the same as the ones that come in platform.system but lowercased. Paths are also expanded using os.path.expanduser which means special symbols like ~ will be expanded in both Window and Linux.
Note if you have a path which can be applied across platforms, then you can define a single config "cross": "~/.bashrc".
list
Once you have a dotfiles configuration and configuration directory you can run list:
❯ dotfiles --config examples/dotfiles-sync.json --config_dir examples/configs list
[18:58:55] INFO Listing Configurations
INFO .bashrc: examples/configs/.bashrc => /home/kiran/.bashrc (ConfigurationMatchStatus.SYNCHRONIZABLE | ConfigurationFileType.FILE)
INFO .vimrc: examples/configs/.vimrc => /home/kiran/.vimrc (ConfigurationMatchStatus.SYNCHRONIZABLE | ConfigurationFileType.FILE)
INFO pgcli: examples/configs/pgcli => /home/kiran/.config/pgcli (ConfigurationMatchStatus.SYNCHRONIZABLE | ConfigurationFileType.DIRECTORY)
SYNCHRONIZABLE means it looks like it is possible to synchronise this file and FILE tells us the type of synchronize it's going to do (as oppsosed to DIRECTORY which will do a recursive copy).
sync
If we are happy, then we can do a sync. This will take the files in your configuration directory and allow them to the machine.
❯ dotfiles --config examples/dotfiles-sync.json --config_dir examples/configs sync
[18:59:41] INFO Copying File examples/configs/.bashrc => /home/kiran/.bashrc
INFO Copying File examples/configs/.vimrc => /home/kiran/.vimrc
INFO Copying Directory examples/configs/pgcli => /home/kiran/.config/pgcli
Syncing Configuration... ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 100% 0:00:00
update
You may want to also do the reverse and update your configuration directory with the files on your current machine. This can be done using update:
❯ dotfiles --config examples/dotfiles-sync.json --config_dir examples/configs update
[19:01:47] INFO Copying File /home/kiran/.bashrc => examples/configs/.bashrc
INFO Copying File /home/kiran/.vimrc => examples/configs/.vimrc
INFO Copying Directory /home/kiran/.config/pgcli => examples/configs/pgcli
Updating Configuration Directory: examples/configs ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 100% 0:00:00
Other
Disabling Items
Configuration Items can be disabled from being applied within the config file.
{
"config":
{
"zsh/.p10k.zsh":
{
"linux": "~/.p10k.zsh",
"disabled": true
}
}
}
Filtering Items
By default dotfiles will assume you want to run configuration on all items (unless explictely disabled). If you would like to only apply certain configurations then you can pass the keys of the configs you want to --filter:
❯ dotfiles -c $HOME/projects/dotfiles/dotfiles-sync.json --filter "bash/.profile" "pgcli/config" -w $HOME/projects/dotfiles/ sync
[14:54:59] INFO Copying File /home/kiran/projects/dotfiles/bash/.profile => /home/kiran/.profile
INFO Copying File /home/kiran/projects/dotfiles/pgcli/config => /home/kiran/.config/pgcli/config
Syncing Configuration... ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 100% 0:00:00
Environment Variables
It can be cumbersome to type out / remember where your dotfiles directory is on each machine. There are two environment variables to make life easier which you can set on a system level:
export DOTFILESSYNC_CONFIG= # path to the dotfiles-sync.json
export DOTFILESSYNC_DIR= # path to your dotfiles which should be synced
This means makes invocation of this dotfiles-sync much cleaner:
dotfiles sync
Metadata
Release files for dotfiles-sync 0.0.15
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| dotfiles-sync-0.0.15.tar.gz | 9.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dotfiles_sync-0.0.15-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 20.3 kB
Release files / dotfiles-sync-0.0.15.tar.gz
| Download URL | dotfiles-sync-0.0.15.tar.gz |
|---|---|
| Size | 9.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
02b748a458a5e55e62e37ee540f45e0488287ce8675d46f872f3e87678197a7d
|
|
BLAKE2b-256 checksum How to use checksums |
3a6493086686413209c6178fe618b8e789a2d1cdaf8f635bc2b8966de26e557b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.25.1 setuptools/49.2.1 requests-toolbelt/0.9.1 tqdm/4.54.1 CPython/3.9.1
|
Release files / dotfiles_sync-0.0.15-py3-none-any.whl
| Download URL | dotfiles_sync-0.0.15-py3-none-any.whl |
|---|---|
| Size | 10.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7034e310691af6abb42f86aef2702b4046c4acb3dca6b81dad55a5dd73286b63
|
|
BLAKE2b-256 checksum How to use checksums |
86f992d803e0271fcea412249307632b4d416562b4c6a7a50d5960cddfc300ac
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.25.1 setuptools/49.2.1 requests-toolbelt/0.9.1 tqdm/4.54.1 CPython/3.9.1
|
Security for dotfiles-sync 0.0.15
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.