fix: update example compose files for MariaDB10.2

examples/laravel5/docker-compose.yml

@@ -29,20 +29,7 @@ services:
             - ../:/code
         networks:
             - [PROJECT_NAME]-internal
-    # Optional DB Container
-    # For projects that the database required isn't available in dev-ops, we can
-    # leverage our own database, like below using MariaDB 10.2.
-    [PROJECT_NAME]-mariadb102:
-        image: mariadb:10.2
-        container_name: sourcetoad_[PROJECT_NAME]_mariadb102
-        ports:
-          - "33102:3306"
-        environment:
-          - MYSQL_ROOT_PASSWORD=root
-          - MYSQL_USER=mariadb_user
-          - MYSQL_PASSWORD=mariadb_pass
-        networks:
-          - [PROJECT_NAME]-internal
+            - st-mariadb-102            
 # These are networks that you are leveraging from outside (external) locations.
 # The dev-ops repo is already running, so these networks already exist. We tell
 # docker which networks of the dev-ops repo we need.
@@ -53,4 +40,7 @@ networks:
       name: nginx-proxy
   st-redis-32:
     external:
-      name: st-redis-32
+      name: st-redis-32
+  st-mariadb-102:
+    external:
+      name: st-mariadb-102

examples/yii2/docker-compose.yml

@@ -29,7 +29,7 @@ services:
             - ../:/code
         networks:
             - [PROJECT_NAME]-internal
-            - st-mariadb-101
+            - st-mariadb-102
             - st-redis-32
 # These are networks that you are leveraging from outside (external) locations.
 # The dev-ops repo is already running, so these networks already exist. We tell
@@ -42,6 +42,6 @@ networks:
     st-redis-32:
         external:
             name: st-redis-32
-    st-mariadb-101:
+    st-mariadb-102:
         external:
-            name: st-mariadb-101
+            name: st-mariadb-102