Own config files
The config role manages several configuration files. To keep your own changes in them, there are two options:
- Recommended: create your own branch of this repository (
git checkout -b my-branch), change the files inansible/roles/config/filesandansible/roles/config/templates, and commit them. To get updates, mergemaster(or a release tag) into your branch. You keep your changes and still receive improvements to the same files; on a conflict, pick your version, the incoming one, or both. - Not recommended: stop Proveasio from managing a file by listing its section in
config_tasks_excludeinansible/vars/overrides.yml(the names are in the config role). The file then never gets updates.zshcannot be excluded, because it is required; to keep your own.zshrc, use option 1 and changeansible/roles/config/templates/zshrc.j2.
Whichever you choose, a file that Proveasio changes is first backed up to ~/.configs_backup, see Backups.
The Neovim config (based on AstroNvim) has its own repository. Fork it and change it, or use a different config entirely. For details see Neovim usage.
To use your own repository, set neovim_config_url and neovim_config_version in ansible/vars/overrides.yml. To use a directory on your machine instead, set:
neovim_config_source: local
neovim_config_local_path: /home/you/my-nvim
The directory is copied to ~/.config/<neovim_config_appname> on every run. The copy adds and overwrites files but never deletes any in the target. If you switch from a git config to a local one, the files of the old clone stay there, including its .git directory. Delete the target directory before the run to start clean.
The shared OpenCode config (agents, skills, plugins, MCP servers) has its own repository, Ziwi01/opencode-config. Fork it like the Neovim config and set opencode_config_url and opencode_config_version in ansible/vars/overrides.yml. To work on a clone on your machine instead, set:
opencode_config_source: local
opencode_config_local_path: /home/you/projects/opencode-config
The local source is not copied: install.sh runs from that directory and the links point into it.
With the git source, the clone in ~/.local/share/opencode-config is managed by Proveasio. If opencode wrote into it (for example opencode mcp add --global), the next run stops on the local changes. Move the change to your own clone and commit it there.
Per-machine additions go in ~/.config/opencode and are not touched: AGENTS.md, skills/, plugins/, opencode.local.json, cli.local.json and skill-repos.local.txt. See the repository README.