Paden
Waar de configuratie, formulieren, playbooks, uploads en back-ups staan
Wijzig deze om een deel van de gegevens op een ander volume te bewaren, bijvoorbeeld back-ups en uploads op grotere of goedkopere opslag.
Voorbeeld
Back-ups en geüploade bestanden op een apart volume, de rest van de gegevens in de gebruikelijke persistente map. In docker-compose.yml:
environment:
- BACKUP_PATH=/data/backups
- FORMS_BACKUP_PATH=/data/forms_backups
- UPLOAD_PATH=/data/uploads
volumes:
- /srv/ansibleforms-data:/data
Een nieuw pad geldt alleen voor nieuwe bestanden: wat al in de oude map staat, wordt niet verplaatst, dus kopieer het zelf over.
Variabelen
Elke variabele van deze groep, met het type, de standaardwaarde en de beschrijving:
| Variabele | Keuzes/Standaardwaarden | Opmerkingen |
|---|---|---|
| BACKUP_PATH string | Standaard: %PERSISTENT_FOLDER%/backups | Backups folder
AnsibleForms can backup the database and forms. This is the path where the backups are stored. The backup folder is created at first start if not present and a timestamp folder is created for each backup. |
| CONFIG_PATH string added in version 6.1.0 | Standaard: %PERSISTENT_FOLDER%/config.yaml | config.yaml path
The config.yaml file contains application configuration (categories, roles, constants). |
| FORMS_FOLDER_PATH string added in version 6.1.0 | Standaard: %PERSISTENT_FOLDER%/forms | Forms folder
The directory where individual form YAML files are stored. Forms can be organized in subdirectories within this folder. |
| FORMS_STAGING_PATH string added in version 6.1.0 | Standaard: %PERSISTENT_FOLDER%/forms_staging | Forms staging folder
When forms come from a git repository, a form created or edited in the designer is written here first and only lands in the repository once it is pushed. The loader reads this folder alongside the repository ones, so a staged form is usable immediately. |
| FORMS_BACKUP_PATH string added in version 4.0.3 | Standaard: %PERSISTENT_FOLDER%/forms_backups | Form backups folder
When backups are made, they end up in this path |
| HOME_PATH string added in version 3.0.0 | Standaard: OS Homedir path | Home folder
AnsibleForms generates an sshkey at first start, is one is not present, so you can have a git connection or other password-less connection. |
| REPO_PATH string added in version 3.0.0 | Standaard: %PERSISTENT_FOLDER%/repositories | Repositories folder
This path is the root path for your local repositories, allowing you to integrate data with git repositories. |
| VARS_FILES_PATH string added in version 6.1.0 | Standaard: %PERSISTENT_FOLDER%/vars | Vars files folder
Base directory for resolving relative paths in form varsFiles property. Absolute paths in varsFiles are used as-is. Relative paths are resolved against this directory. Allows centralized management of shared variable files across forms. |
| INVENTORY_PATH string added in version 7.0.0 | Standaard: %PERSISTENT_FOLDER%/inventories | Inventories folder
The local inventories folder: one folder per inventory (staging/inventory.yaml, with its group_vars and host_vars), edited in the designer’s Inventories section, next to the repositories used for inventories (each of them an inventory). A playbook form names one with |
| WORKFLOWS_PATH string added in version 7.0.0 | Standaard: %PERSISTENT_FOLDER%/workflows | Workflows folder
The local workflows folder: workflow files in the AWX export syntax (workflow_job_templates, a job template node running one of the designer’s playbooks), edited in the designer’s Workflows section, next to the repositories used for workflows. A workflow form runs one with |
| ANSIBLE_PATH string | Standaard: %PERSISTENT_FOLDER%/playbooks | Where an RTE finds the playbooks
Read by an RTE ( |
| UPLOAD_PATH string added in version 4.0.16 | Standaard: %PERSISTENT_FOLDER%/uploads | Uploads folder
Since 4.0.16, a new field type is introduced that allows file uploads. The files are uploaded in this path. |