Stacks are defined in a list of objects
This is a stack ident, it should not be changed. If not set, it comes from the app name, and from the dir if no apps. Should not contains any special char, except - (or _). This is used to name the app (docker, dns, etc ...)
Must be at least 2
characters long
Directory where the docker-compose.run.yml file is generated. Can be used to move stack directories (cold move). Default comes from the name.
Shortcut to use an application without modifying it's default parameters. First optional part is module collection, and after the ':', it's the name/path to the aplication inside the module
Determine a list of tags to apply
Define a list of tags. You can interact in few ways with tags. Tags can support boths syntaxes at the same time.
{
"tags": [
"my_tagg",
"~my_prefix_tag",
"my_collection:my_prefix_tag",
{
"other_tag": {
"specific_conf": "val1"
}
},
{
"my_collection:another_tag": null
},
{
"~ignore_this_tag": {
"specific_conf": "val1"
}
}
]
}
Each additional property must conform to the following schema
Tag definition. It support two formats at the same time: as string or dict. If the name is prefixed with a !
, then it is removed from the processing list (both vars, docker-file and jsonnet processing).
Just pass the tag you want to apply as string. This form does not allow jsonnet ovar override
Completely disable a tag from the processing list, whatever how many instances there are.
Must match regular expression:[~].*
Reference a tag from a specific collection.See: Specific tag documentation for further informations.
Must match regular expression:^.*:.*$
Will find the best matching tag.See: Specific tag documentation for further informations.
Must match regular expression:.*
{
"tags": [
"my_tagg",
"~my_prefix_tag",
"my_collection:my_prefix_tag"
]
}
Define a tag. The key represent the name of the tag, while it's value is passed as vars during jsonnet processing. This form allow jsonnet ovar override
{
"tags": [
{
"other_tag": {
"specific_conf": "val1"
}
},
{
"my_collection:another_tag": null
},
{
"~ignore_this_tag": {
"specific_conf": "val1"
}
}
]
}
All properties whose name matches the following regular expression must respect the following conditions
Property name regular expression:[~].*
Completely disable a tag from the processing list, whatever how many instances there are.
Pass extra vars for during jsonet tag processing.
No vars are added for this jsonnet tag processing.
All properties whose name matches the following regular expression must respect the following conditions
Property name regular expression:^.*:.*$
Reference a tag from a specific collection.See: Specific tag documentation for further informations.
Pass extra vars for during jsonet tag processing.
No vars are added for this jsonnet tag processing.
All properties whose name matches the following regular expression must respect the following conditions
Property name regular expression:.*
Will find the best matching tag.See: Specific tag documentation for further informations.
Pass extra vars for during jsonet tag processing.
No vars are added for this jsonnet tag processing.
Determine a list of tags to apply
Define a list of tags. You can interact in few ways with tags. Tags can support boths syntaxes at the same time.
{
"tags": [
"my_tagg",
"~my_prefix_tag",
"my_collection:my_prefix_tag",
{
"other_tag": {
"specific_conf": "val1"
}
},
{
"my_collection:another_tag": null
},
{
"~ignore_this_tag": {
"specific_conf": "val1"
}
}
]
}
Each additional property must conform to the following schema
Tag definition. It support two formats at the same time: as string or dict. If the name is prefixed with a !
, then it is removed from the processing list (both vars, docker-file and jsonnet processing).
Just pass the tag you want to apply as string. This form does not allow jsonnet ovar override
Completely disable a tag from the processing list, whatever how many instances there are.
Must match regular expression:[~].*
Reference a tag from a specific collection.See: Specific tag documentation for further informations.
Must match regular expression:^.*:.*$
Will find the best matching tag.See: Specific tag documentation for further informations.
Must match regular expression:.*
{
"tags": [
"my_tagg",
"~my_prefix_tag",
"my_collection:my_prefix_tag"
]
}
Define a tag. The key represent the name of the tag, while it's value is passed as vars during jsonnet processing. This form allow jsonnet ovar override
{
"tags": [
{
"other_tag": {
"specific_conf": "val1"
}
},
{
"my_collection:another_tag": null
},
{
"~ignore_this_tag": {
"specific_conf": "val1"
}
}
]
}
All properties whose name matches the following regular expression must respect the following conditions
Property name regular expression:[~].*
Completely disable a tag from the processing list, whatever how many instances there are.
Pass extra vars for during jsonet tag processing.
No vars are added for this jsonnet tag processing.
All properties whose name matches the following regular expression must respect the following conditions
Property name regular expression:^.*:.*$
Reference a tag from a specific collection.See: Specific tag documentation for further informations.
Pass extra vars for during jsonet tag processing.
No vars are added for this jsonnet tag processing.
All properties whose name matches the following regular expression must respect the following conditions
Property name regular expression:.*
Will find the best matching tag.See: Specific tag documentation for further informations.
Pass extra vars for during jsonet tag processing.
No vars are added for this jsonnet tag processing.
Do not declare any tags
{
"tags": null
}
Determine a list of tags to apply
Define a list of tags. You can interact in few ways with tags. Tags can support boths syntaxes at the same time.
{
"tags": [
"my_tagg",
"~my_prefix_tag",
"my_collection:my_prefix_tag",
{
"other_tag": {
"specific_conf": "val1"
}
},
{
"my_collection:another_tag": null
},
{
"~ignore_this_tag": {
"specific_conf": "val1"
}
}
]
}
Each additional property must conform to the following schema
Tag definition. It support two formats at the same time: as string or dict. If the name is prefixed with a !
, then it is removed from the processing list (both vars, docker-file and jsonnet processing).
Just pass the tag you want to apply as string. This form does not allow jsonnet ovar override
Completely disable a tag from the processing list, whatever how many instances there are.
Must match regular expression:[~].*
Reference a tag from a specific collection.See: Specific tag documentation for further informations.
Must match regular expression:^.*:.*$
Will find the best matching tag.See: Specific tag documentation for further informations.
Must match regular expression:.*
{
"tags": [
"my_tagg",
"~my_prefix_tag",
"my_collection:my_prefix_tag"
]
}
Define a tag. The key represent the name of the tag, while it's value is passed as vars during jsonnet processing. This form allow jsonnet ovar override
{
"tags": [
{
"other_tag": {
"specific_conf": "val1"
}
},
{
"my_collection:another_tag": null
},
{
"~ignore_this_tag": {
"specific_conf": "val1"
}
}
]
}
All properties whose name matches the following regular expression must respect the following conditions
Property name regular expression:[~].*
Completely disable a tag from the processing list, whatever how many instances there are.
Pass extra vars for during jsonet tag processing.
No vars are added for this jsonnet tag processing.
All properties whose name matches the following regular expression must respect the following conditions
Property name regular expression:^.*:.*$
Reference a tag from a specific collection.See: Specific tag documentation for further informations.
Pass extra vars for during jsonet tag processing.
No vars are added for this jsonnet tag processing.
All properties whose name matches the following regular expression must respect the following conditions
Property name regular expression:.*
Will find the best matching tag.See: Specific tag documentation for further informations.
Pass extra vars for during jsonet tag processing.
No vars are added for this jsonnet tag processing.
Do not declare any tags
{
"tags": null
}
Environment configuration. Paasify leave two choices for the configuration, either use the native dict configuration or use the docker-compatible format
Configure variables as a list. This is the recommended way asit preserves the variable parsing order, useful for templating. This format allow multiple configuration format.
{
"env": [
{
"MYSQL_ADMIN_USER": "MyUser"
},
{
"MYSQL_ADMIN_DB": "MyDB"
},
{
"MYSQL_ENABLE_BACKUP": true
},
{
"MYSQL_BACKUPS_NODES": 3
},
{
"MYSQL_NODE_REPLICA": null
},
"MYSQL_WELCOME_STRING=Is alway a string"
]
}
Each additional property must conform to the following schema
Environment configuration. Paasify leave two choices for the configuration, either use the native dict configuration or use the docker-compatible format
Simple key value variable declaration, under the form of: {KEY: VALUE}. This does preserve value type.
{
"env": [
{
"MYSQL_ADMIN_USER": "MyUser"
},
{
"MYSQL_ADMIN_DB": "MyDB"
}
]
}
All properties whose name matches the following regular expression must respect the following conditions
Property name regular expression:^[A-Za-z_][A-Za-z0-9_]*$
Value must be serializable type
Value must be a string, under the form of: KEY=VALUE. This does not preserve value type.
Must match regular expression:^[A-Za-z_][A-Za-z0-9_]*=.*$
{
"env": [
"MYSQL_ADMIN_USER=MyUser",
"MYSQL_ADMIN_DB=MyDB"
]
}
Configure variables as a dict. This option is only proposed for compatibility reasons. It does not preserve the order of the variables.
{
"env": {
"MYSQL_ADMIN_USER": "MyUser",
"MYSQL_ADMIN_DB": "MyDB",
"MYSQL_ENABLE_BACKUP": true,
"MYSQL_BACKUPS_NODES": 3,
"MYSQL_NODE_REPLICA": null
}
}
Shortcut to use an application without modifying it's default parameters. First optional part is module collection, and after the ':', it's the name/path to the aplication inside the module
Must match regular expression:^([^:]+:)?(.*)$