Reference

Files and directories

Where instamix keeps things on a machine, and the files it writes into a tree.

On the machine#

PathWhat is there
~/.config/instamix/configthe settings for everything
.instamixconfigthe settings for a repository: the nearest one from the script’s directory up to the root of its git repository
~/.cache/instamix/envs/the environments env builds, each named by a digest of what it holds
~/.cache/instamix/lsp/the trees the language server lints and completes from
~/.cache/instamix/proxythe files the proxy has fetched
~/.instamix/proxy.dbthe proxy’s lists and its log of refusals (SQLite)
~/.instamix/hub.dbthe hub’s database (SQLite)
~/.local/share/instamix/repos/the playbook repositories imix repo add clones

In an environment#

Each directory under ~/.cache/instamix/envs/ holds:

PathWhat it is
venv/the virtualenv, with ansible-core and the pip requirements
requirements.inwhat was asked for
requirements.lockwhat that resolved to, with hashes
env.jsonwhat was built
collections/, roles/what a base brings, and nothing else

In a generated tree#

PathWhere it comes from
inventory, ansible.cfgadded unless the script declares its own, or --bare
requirements.ymlthe galaxy requirements, when there are any
requirements.txtthe pip requirements, unless the script declares one
site.yml, group_vars/<group>.ymlwritten from the stages, groups and variables a script describes
roles/, collections/what the script declares, and what install fetches
galaxy.lockwhat was installed, for which requirements
.instamixwhat generate wrote, so the next one removes what the script no longer declares; left out of archives

In the source#

PathWhat it is
api/openapi.jsonthe contract: imix spec -o api/openapi.json writes it again (download)
instamix_bases.pythe pins of the community bases; tools/update_bases.py writes it again
deploy/the images, the compose file and the kustomize base, components and overlays
site/this site

The source of this page

    Type to search. ↑ ↓ to move, enter to open.