docker: Coolify対応のためDockerfileビルドに移行しbind mount依存を排除

- ルートDockerfileで npm ci をビルド時に一元実行（node_modulesの競合破損を防止）
- web/api/workerをYAMLアンカーで共通ビルド構成に変更し、.:/workspace のbind mountを削除
- vinextは --hostname でバインド指定（--host は無視される）
- minio-initを削除（APIがbucketを自動作成）し、MinIOをexposeのみの内部公開に変更
- .dockerignore を追加し、.wranglerディレクトリをDockerfile内で事前作成

.env.example

@@ -6,6 +6,10 @@ NEXT_PUBLIC_AUTH_MODE=demo
 
 # --- Storage (MinIO via docker compose) -------------------------------------
 # Leave DATABASE_URL empty to run with an in-memory store instead of Postgres.
+# docker-compose.yml keeps MinIO internal-only (no published ports/domain) and
+# all uploads flow through the API, so the API uses the internal endpoint.
+# When running the API on the host instead of inside compose, re-add MinIO's
+# host ports (9000/9001) to docker-compose.yml first.
 DATABASE_URL=postgres://altdock:altdock@localhost:5432/altdock
 STORAGE_MODE=s3
 S3_ENDPOINT=http://localhost:9000
@@ -17,7 +21,7 @@ S3_FORCE_PATH_STYLE=true
 # MinIO root credentials, consumed by docker-compose.yml. CHANGE in production.
 MINIO_ROOT_USER=minioadmin
 MINIO_ROOT_PASSWORD=minioadmin123
-# Only needed when MinIO is behind a reverse proxy / domain (e.g. on Coolify):
+# Only needed when MinIO is exposed behind a reverse proxy / domain:
 MINIO_SERVER_URL=
 MINIO_BROWSER_REDIRECT_URL=