Skip to main content

Configuration as code

Configuration-as-Code

The idea behind Configuration-as-Code (CaC) is that configuration data, traditionally managed manually or through proprietary tools, should instead be managed using code. In other words, it’s about treating configuration data just like we treat application code.

Unifie recommends to use Configuration-as-Code methodology.

You can enable it in application template Settings

git-ui

In unifie we separate deployment to 2 entities:

  • Application template
  • Application configuration (variables values)

Unifie store separately application template and application configuration. Template stored in files, and we recommend to use git to track changes in this files.

Benefits

If you store your templates in git:

  • you can edit templates files in external IDE and than push changes to unifie.
  • you can use git branches to different versions of your deployments
  • you can share your project with other unifie users.

Get templates files

You can browse application template files on Files tab

git-ui