WordPress stack database deployment naming problems

[esackbauer]

When I deploy the first WordPress stack "name1", the Database volume is called "db_data", but it should be named "name1_db_data" according to the naming conventions of the rest of the stack.
When I deploy a second WordPress stack "name2", the database volume of the new container "name2_db_1" points to that same volume "db_data" and an empty unused volume correctly named "name2_db_data" is created.

[trydalch]

I'm also experiencing this issue. Was exposed when I attempted to deploy multiple wordpress stacks and they all tried to use the same volume, even though volumes were created using the correct name.

It's an easy fix. Just enter the site_db container, click duplicate/edit, and then update the volume to the correct one and deploy the container and select replace when prompted.