該賞金到期in 4天。回答這個問題有資格獲得 50聲望獎勵。 karambaq想引起更多人對這個問題的關注：
仍然不明白使用 docker-compose 解決問題的正確方法。
我在更新生產模式 VueJS 應用程式時遇到問題。不是每次都跑
docker-compose up --build
我應該做
docker-compose down
docker volume rm mkstat_frontend_dist
docker-compose up --build
并且在此期間有很多停機時間，所以我想解決這個問題。我知道這是因為體積，但不知道如何解決這個問題。我試過只是洗掉這個卷，然后 nginx 回應
directory index of "/app/dist/" is forbidden
這是我的應用程式結構：
.
├── docker/
├── docker-compose.back.yml
├── docker-compose.dev.yml
├── docker-compose.yml
├── fresh_dump.sql
├── init-letsencrypt.sh
├── mkstat_backend/
├── mkstat_frontend/
├── redis.conf
這是我的 prod docker-compose 檔案：
docker-compose.yml
version: "3.8"
services:
backend:
container_name: backend
restart: always
build:
context: ./mkstat_backend
dockerfile: Dockerfile.prod
volumes:
- static:/app/static
- media:/app/media
env_file:
- ./mkstat_backend/.env.prod
depends_on:
- db
db:
container_name: db
restart: always
build:
context: ./docker/postgres
dockerfile: Dockerfile
volumes:
- pgdata:/var/lib/postgresql/data/
ports:
- "5432:5432"
env_file:
- ./mkstat_backend/.env.prod
frontend:
container_name: frontend
build:
context: ./mkstat_frontend
dockerfile: Dockerfile.prod
volumes:
- frontend_dist:/app/dist
depends_on:
- backend
nginx:
image: nginx:alpine
restart: unless-stopped
command: '/bin/sh -c ''while :; do sleep 6h & wait $${!}; nginx -s reload; done & nginx -g "daemon off;"'''
container_name: nginx
ports:
- "80:80"
- "443:443"
volumes:
- ./docker/nginx/nginx.conf:/etc/nginx/conf.d/default.conf
- ./docker/certbot/conf:/etc/letsencrypt
- ./docker/certbot/www:/var/www/certbot
- static:/var/html/static
- media:/var/html/media
- frontend_dist:/app/dist
depends_on:
- backend
- frontend
certbot:
container_name: certbot
image: certbot/certbot
restart: unless-stopped
entrypoint: "/bin/sh -c 'trap exit TERM; while :; do certbot renew; sleep 12h & wait $${!}; done;'"
volumes:
- ./docker/certbot/conf:/etc/letsencrypt
- ./docker/certbot/www:/var/www/certbot
redis:
image: redis:latest
restart: always
container_name: redis
command: [
"bash",
"-c",
"
redis-server
--requirepass $${REDIS_PASS}
",
]
volumes:
- redis:/var/lib/redis/data
- ./redis.conf:/usr/local/etc/redis/redis.conf
ports:
- "6379"
env_file:
- ./mkstat_backend/.env.prod
worker:
build:
context: ./mkstat_backend
command: celery -A mkstat worker -B -l info -s /tmp/celerybeat-schedule
restart: always
container_name: celery
depends_on:
- db
- redis
- backend
volumes:
- ./mkstat_backend:/app
env_file:
- ./mkstat_backend/.env.prod
volumes:
pgdata:
static:
media:
frontend_dist:
redis:
Vue Dockerfile：
FROM node:lts-alpine as build
WORKDIR /app
ENV PATH /app/node_modules/.bin:$PATH
COPY package.json /app/package.json
RUN npm install --silent
RUN npm install @vue/[email protected] -g
COPY . /app
RUN npm run build
提前致謝。
uj5u.com熱心網友回復：
TL; 博士
docker-compose down
docker volume rm mkstat_frontend_dist
docker-compose up --build
... 不是最佳的，因為服務將在構建期間關閉。這些服務不需要為構建而取消，因此：
docker-compose build
docker-compose down
docker volume rm mststat_frontend_dist
docker-compose up -d
...會稍微更有效，因為服務只會脫機以清除舊容器和卷，然后將從預先構建的映像創建新容器。
dist據我所知，不需要支持檔案的卷，您可以將其洗掉。dist部署中提供的檔案將是映像中內置的檔案，而不必在每次重新部署時洗掉卷。
如果您將鏡像推送到Docker Hub或其他 docker 注冊表，則鏡像已經構建，您無需在重新部署期間重新構建。您的流程可能如下所示：
- 在您的 PC 上構建 docker 鏡像
- 將 docker 鏡像推送到 docker 注冊表
- 在服務器上拉取 docker 鏡像
docker-compose down洗掉舊容器的服務docker-compose up -d從影像啟動新容器
對于 nginx 的生產部署，這是我用作基礎的示例配置：
worker_processes 1;
error_log /var/log/nginx/error.log warn;
pid /var/run/nginx.pid;
events {
worker_connections 1024;
}
http {
map $http_upgrade $connection_upgrade {
default upgrade;
'' close;
}
include /etc/nginx/mime.types;
default_type application/octet-stream;
log_format main '$remote_addr - $remote_user [$time_local] "$request" '
'$status $body_bytes_sent "$http_referer" '
'"$http_user_agent" "$http_x_forwarded_for"';
client_max_body_size 0;
access_log /var/log/nginx/access.log main;
sendfile on;
keepalive_timeout 65;
upstream web {
server web:80 max_fails=3;
}
server {
listen *:80;
listen [::]:80;
server_name _;
return 301 https://$host$request_uri;
}
add_header X-Frame-Options SAMEORIGIN;
add_header X-Content-Type-Options nosniff;
add_header Strict-Transport-Security "max-age=31536000; includeSubdomains; preload";
add_header Content-Security-Policy "default-src 'self';";
server {
listen *:443 ssl http2;
listen [::]:443 ssl http2;
server_name *.example.com example.com;
charset utf-8;
error_page 404 = @notfound;
server_tokens off;
proxy_buffer_size 128k;
proxy_buffers 4 256k;
proxy_busy_buffers_size 256k;
ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem;
ssl_session_cache shared:SSL:50m;
ssl_session_timeout 1d;
ssl_session_tickets off;
ssl_dhparam /etc/nginx/ssl/dhparam.pem;
ssl_prefer_server_ciphers on;
ssl_protocols TLSv1.2 TLSv1.3;
ssl_ciphers 'ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA:ECDHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA256:DHE-RSA-AES256-SHA:ECDHE-ECDSA-DES-CBC3-SHA:ECDHE-RSA-DES-CBC3-SHA:EDH-RSA-DES-CBC3-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:DES-CBC3-SHA:!DSS';
resolver 127.0.0.11 1.1.1.1 8.8.8.8 8.8.4.4 valid=86400s;
resolver_timeout 5s;
ssl_stapling on;
ssl_stapling_verify on;
ssl_trusted_certificate /etc/letsencrypt/live/example.com/chain.pem;
error_page 404 = @notfound;
location @notfound {
return 301 /;
}
location /healthz {
allow 127.0.0.1;
deny all;
stub_status;
}
location / {
proxy_http_version 1.1;
proxy_set_header HOST $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $connection_upgrade;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Forwarded-Server $host;
proxy_set_header X-Forwarded-Port $server_port;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_pass http://web/;
}
}
}
該
nginx.conf示例是一些第三方滲透測驗的結果，例如server_tokens（默認值：on）將被標記，允許舊版本的 TLS/SSL 將被標記，未設定Content-Security-Policy標頭將被標記等。
轉載請註明出處，本文鏈接：https://www.uj5u.com/ruanti/365426.html
標籤：docker vue.js nginx docker-compose dockerfile