examples: Favor configs over builds

There doesn't seem to be a need to prefer building custom containers,
just to add a config file, a need that is easily solved with compose
configs. Configs are still managed through git, just no new container
needs to be built, slightly simplifying things.

Signed-off-by: Olliver Schinagl <oliver@schinagl.nl>

.examples/docker-compose/with-nginx-proxy/mariadb/apache/docker-compose.yml

@@ -49,13 +49,16 @@ services:
       - redis
 
   proxy:
-    build: ./proxy
+    image: nginxproxy/nginx-proxy:alpine
     restart: always
     ports:
       - 80:80
       - 443:443
     labels:
       com.github.jrcs.letsencrypt_nginx_proxy_companion.nginx_proxy: "true"
+    configs:
+      - source: proxy
+        target: /etc/nginx/conf.d/uploadsize.conf
     volumes:
       - certs:/etc/nginx/certs:z,ro
       - vhost.d:/etc/nginx/vhost.d:z
@@ -93,6 +96,10 @@ services:
 #    networks:
 #      - proxy-tier
 
+configs:
+  proxy:
+    file: uploadsize.conf
+
 volumes:
   db:
   nextcloud:

.examples/docker-compose/with-nginx-proxy/mariadb/apache/proxy/Dockerfile

@@ -1,3 +0,0 @@
-FROM nginxproxy/nginx-proxy:alpine
-
-COPY uploadsize.conf /etc/nginx/conf.d/uploadsize.conf