[docs] minor fixes in Dockerfile and some others (#4473)

docs/docs/self-hosting/guides/web-app.md

@@ -49,7 +49,7 @@ ENV NEXT_PUBLIC_ENTE_ACCOUNTS_ENDPOINT=https://your-domain.com
 
 RUN yarn cache clean
 RUN yarn install --network-timeout 1000000000
-RUN yarn build:photos && yarn build:auth && yarn build:accounts && yarn build:cast
+RUN yarn build:photos && yarn build:accounts && yarn build:auth && yarn build:cast
 
 FROM node:20-bookworm-slim
 
@@ -74,10 +74,13 @@ EXPOSE ${AUTH}
 ENV CAST=3003
 EXPOSE ${CAST}
 
+# The albums app does not have navigable pages on it, but the 
+# port will be exposed in-order to self up the albums endpoint 
+# `apps.public-albums` in museum.yaml configuration file.
 ENV ALBUMS=3004
 EXPOSE ${ALBUMS}
 
-CMD ["sh", "-c", "serve /app/photos -l tcp://0.0.0.0:${PHOTOS} & serve /app/accounts -l tcp://0.0.0.0:${ACCOUNTS} & serve /app/albums -l tcp://0.0.0.0:3003 & serve /app/auth -l tcp://0.0.0.0:${AUTH} & serve /app/cast -l tcp://0.0.0.0:${CAST}"]
+CMD ["sh", "-c", "serve /app/photos -l tcp://0.0.0.0:${PHOTOS} & serve /app/accounts -l tcp://0.0.0.0:${ACCOUNTS} & serve /app/auth -l tcp://0.0.0.0:${AUTH} & serve /app/cast -l tcp://0.0.0.0:${CAST}"]
 ```
 
 The above is a multi-stage Dockerfile which creates a production ready static output
@@ -214,6 +217,10 @@ will take care of that.
 ```sh
 photos.yourdomain.com {
 	reverse_proxy http://localhost:3001
+    # for logging
+    log {
+        level error
+    }
 }
 
 auth.yourdomain.com {