Solved database feature naming bug

This commit is contained in:
2025-05-09 19:00:01 +02:00
parent e7c193f409
commit 27bfee2438
19 changed files with 26 additions and 24 deletions

View File

@@ -1,10 +1,10 @@
{# This template needs to be included in docker-compose.yml #}
networks:
{% if applications | is_feature_enabled('central_database',application_id) | bool and database_type is defined %}
{% if applications | is_feature_enabled('central_database',application_id) and database_type is defined %}
central_{{ database_type }}:
external: true
{% endif %}
{% if applications[application_id].get('features', {}).get('ldap', false) | bool and applications.ldap.network.docker | bool %}
{% if applications[application_id].get('features', {}).get('ldap', false) and applications.ldap.network.docker | bool %}
central_ldap:
external: true
{% endif %}

View File

@@ -1,5 +1,5 @@
{# This needs to be included in docker-compose.yml which just contain a database volume #}
{% if not (applications[application_id].features.database | default(false)) | bool %}
{% if not applications | is_feature_enabled('central_database',application_id) %}
volumes:
database:
{% endif %}

View File

@@ -1,6 +1,6 @@
{# This template needs to be included in docker-compose.yml which contain a database and additional volumes #}
volumes:
{% if not (applications[application_id].features.database | default(false)) | bool %}
{% if not applications | is_feature_enabled('central_database',application_id) %}
database:
{% endif %}
{{ "\n" }}