Solved network bug

roles/docker-discourse/handlers/main.yml

@@ -1,5 +1,5 @@
 ---
 - name: recreate discourse
   command:
-    cmd: ./launcher rebuild discourse_application
+    cmd: "./launcher rebuild {{discourse_application_container}}"
     chdir: "{{discourse_repository_directory}}"

roles/docker-discourse/tasks/main.yml

@@ -64,6 +64,12 @@
 - name: flush, to recreate discourse app
   meta: flush_handlers
 
+- name: "add {{discourse_application_container}} to network central_postgres"
+  command:
+    cmd: "docker network connect central_postgres {{discourse_application_container}}"
+  ignore_errors: true
+  when: enable_central_database | bool
+  
 - name: "remove central database from {{docker_compose_project_name}}_default"
   command:
     cmd: "docker network disconnect discourse_default central-{{ database_type }}"

roles/docker-discourse/templates/discourse_application.yml.j2

@@ -119,4 +119,4 @@ run:
 
 docker_args:
   - --network={{docker_compose_project_name}}_default
-  - --name=discourse_application
+  - --name={{discourse_application_container}}

roles/docker-discourse/vars/main.yml

@@ -1,4 +1,5 @@
 docker_compose_project_name:      "discourse"
+discourse_application_container:  "discourse_application"
 database_password:                "{{ baserow_database_password }}"
 database_type:                    "postgres"
 discourse_repository_directory:   "{{ path_docker_compose_instances + docker_compose_project_name + '/repository/' }}"