Pārlūkot izejas kodu

fix: S3_ENDPOINT без http://, Caddy /files вместо /s3, S3_PUBLIC_ENDPOINT через api.photoplaces.ru

neyrogovnarik 1 mēnesi atpakaļ
vecāks
revīzija
5d1a4d804a
2 mainītis faili ar 2 papildinājumiem un 2 dzēšanām
  1. 1 1
      deploy/Caddyfile
  2. 1 1
      docker-compose.yml

+ 1 - 1
deploy/Caddyfile

@@ -4,7 +4,7 @@
 
 # API subdomain — прокси на backend + MinIO (HTTP, SSL на Synology)
 http://api.{$DOMAIN} {
-	handle_path /s3/* {
+	handle_path /files/* {
 		reverse_proxy minio:9000 {
 			header_up Host {host}
 			header_up X-Real-IP {remote}

+ 1 - 1
docker-compose.yml

@@ -68,7 +68,7 @@ services:
       APP_ENV: ${APP_ENV:-development}
       DATABASE_URL: postgres://photoplaces:${POSTGRES_PASSWORD:-photoplaces_dev}@postgres:5432/photoplaces?sslmode=disable
       REDIS_URL: redis://:${REDIS_PASSWORD:-photoplaces_dev}@redis:6379/0
-      S3_ENDPOINT: http://minio:9000
+      S3_ENDPOINT: ${S3_ENDPOINT:-minio:9000}
       S3_ACCESS_KEY: photoplaces
       S3_SECRET_KEY: ${MINIO_PASSWORD:-photoplaces_dev}
       S3_BUCKET: photoplaces