.confix Files
#12
PascalSenn
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
.confixFilesConfix provides a set of configuration files that allow you to manage settings on global, repository, project, component, and deployment levels. These files include:
.confixrc,.confix.repository,.confix.project,.confix.component, and.confix.lock.Each configuration file serves a unique purpose in the overall Confix configuration process:
1.
.confixrcThis global configuration file is located in the user's home directory. It is used to define global settings that are applied across all repositories and projects. Settings defined here are inherited by the
.confix.repository,.confix.component, and.confix.projectfiles.You can override project-specific settings by using the
projectfield in the.confixrcfile. In case of multiple.confixrcfiles, settings can be overridden in the parent folder's.confixrcfiles. To signal Confix to look for further.confixrcfiles in parent folders and the home directory, you need to specifyisRoot: false.{ "isRoot": false, "repositories": [ // repositories config check the component repository section ], "componentProviders": [ // componentProviders config check the component discovery section ], "variableProviders": [ // variableProviders config check the variable providers section ], "environments": [ // environments config check the environments section ], "configurationFiles": [ // configurationFiles config check the configuration files section ], "project": { // default project config like in .confix.project, "subprojects": [ // default subprojects config check the subprojects section ] }, "component": { // default component config like in .confix.component } }2.
.confix.repositoryThis configuration file is defined at the root of the repository. It is used to specify repository-specific settings applicable across all projects within the repository. Settings defined here are inherited by the
.confix.componentand.confix.projectfiles.Project-specific settings can be overridden by using the
projectfield in the.confix.repositoryfile. For more information, refer to theRepositoriessection.{ "repositories": [ // repositories config check the component repository section ], "componentProviders": [ // componentProviders config check the component discovery section ], "variableProviders": [ // variableProviders config check the variable providers section ], "environments": [ // environments config check the environments section ], "configurationFiles": [ // configurationFiles config check the configuration files section ], "project": { // default project config like in .confix.project, "subprojects": [ // default subprojects config check the subprojects section ] }, "component": { // default component config like in .confix.component } }3.
.confix.projectThis file is used to configure a specific project. You can find more detailed information about this in the
Projectsection.{ "name": "MyProject", "environments": [ // environments config check the environments section ], "components": { // components config check the components section }, "configurationFiles": [ // configurationFiles config check the configuration files section ], "subprojects": [ // subprojects config check the subprojects section ] }4.
.confix.componentThe
.confix.componentfile is used for configuring individual components. More about this can be found in theComponentssection.{ "name": "MyComponent", "inputs": [ { "type": "graphql" // additional properties specific to the graphql compiler } ], "outputs": [ { "type": "dotnet-options-classes", // additional properties specific to the json output } ] }5.
.confix.lockThe
.confix.lockfile is generated during thebuildoperation and contains all necessary information for deploying the application. The file is used during thebuildoperation to replace the variables in the configuration files with their actual values.It contains the complete configuration that was composed out of all .confixrc and .confix.repository files, except the secrets. The confix lock file is safe to commit to your repository and you have to include it in your container image.
Beta Was this translation helpful? Give feedback.
All reactions