Fixed wrong app name and set kamal config

config/deploy.yml

@@ -1,13 +1,13 @@
 # Name of your application. Used to uniquely configure containers.
-service: vault17
+service: vault171
 
 # Name of the container image (use your-user/app-name on external registries).
-image: vault17
+image: vault171
 
 # Deploy to these servers.
 servers:
   web:
-    - 192.168.0.1
+    - kamaldocker.fritz.box
   # job:
   #   hosts:
   #     - 192.168.0.1
@@ -20,9 +20,9 @@ servers:
 #
 # Don't use this when deploying to multiple web servers (then you have to terminate SSL at your load balancer).
 #
-# proxy:
-#   ssl: true
-#   host: app.example.com
+proxy:
+  ssl: false
+  host: vault171.daboh.ipv64.de
 
 # Where you keep your container images.
 registry:
@@ -36,6 +36,11 @@ registry:
   # password:
   #   - KAMAL_REGISTRY_PASSWORD
 
+logging:
+  driver: json-file
+  options:
+    max-size: "10m"
+
 # Inject ENV variables into containers (secrets come from .kamal/secrets).
 env:
   secret:
@@ -52,7 +57,7 @@ env:
     # WEB_CONCURRENCY: 2
 
     # Match this to any external database server to configure Active Record correctly
-    # Use vault17-db for a db accessory server on same machine via local kamal docker network.
+    # Use vault171-db for a db accessory server on same machine via local kamal docker network.
     # DB_HOST: 192.168.0.2
 
     # Log everything from Rails
@@ -69,7 +74,7 @@ aliases:
 # Use a persistent storage volume for sqlite database files and local Active Storage files.
 # Recommended to change this to a mounted volume path that is backed up off server.
 volumes:
-  - "vault17_storage:/rails/storage"
+  - "/opt/docker/vault171/storage:/rails/storage"
 
 # Bridge fingerprinted assets, like JS and CSS, between versions to avoid
 # hitting 404 on in-flight requests. Combines all files from new and old