You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This request is not a duplicate of an existing issue
I have read the docs and followed them (if applicable)
I have seached the Roots Discourse for answers and followed them (if applicable)
This is not a personal support request that should be posted on the Roots Discourse community
Description
What's wrong?
If we have multiple WordPress sites and one should use a local MariaDB and the other one a remote DB the setup tasks are skipped because of the when condition.
What have you tried?
Changed the condition manually.
Possible solutions
Change the condition in roles/mariadb/tasks/main.yml:75 to: when: (wordpress_sites.items() | count) > (sites_using_remote_db | count)
Temporary workarounds
Change the condition manually.
Use Case
Use one shared host for multiple WordPress sites, but allow single sites to use a remote database without blocking the initiation of the others.
Steps To Reproduce
add two WordPress sites
add a remote database connection to the second instance via
Terms
Description
What's wrong?
If we have multiple WordPress sites and one should use a local MariaDB and the other one a remote DB the setup tasks are skipped because of the
when
condition.What have you tried?
Changed the condition manually.
Possible solutions
Change the condition in
roles/mariadb/tasks/main.yml:75
to:when: (wordpress_sites.items() | count) > (sites_using_remote_db | count)
Temporary workarounds
Change the condition manually.
Use Case
Use one shared host for multiple WordPress sites, but allow single sites to use a remote database without blocking the initiation of the others.
Steps To Reproduce
Expected Behavior
Besides setting up the remote database connection on one site, it should also be set up a local database.
Actual Behavior
It configures the remote database but doesn't set up the local database.
Relevant Log Output
No response
Versions
1.18.0
The text was updated successfully, but these errors were encountered: