Hello,
kindly help me with a solution i have a issue with my nginx it uses
docker-compose with clery and flower dashboard which point to difrent url
the flower url works fine as expected but the main django sever not working
saying page not found
docker-compose
version: '3.9'
services:
api: &api
build:
context: .
dockerfile: docker/prod/Dockerfile
image: 1.dkr.ecr.eu-west-2.amazonaws.com/pro:web
command: gunicorn core.wsgi:application --bind 0.0.0.0:8000 --timeout
420
logging:
driver: "awslogs"
options:
awslogs-region: "region"
awslogs-group: "amazon-linux-proxi"
awslogs-stream: "amazon-linux-proxi"
volumes:
- ./app:/app
ports:
- '8000:8000'
env_file:
- ./.env
restart: unless-stopped
celery:
<<: *api
command: celery -A core worker -l info
ports: []
volumes:
- ./app:/app
env_file:
- ./.env
depends_on:
- api
celery-beat:
<<: *api
user: root
command: celery -A core beat -l info
ports: []
volumes:
- ./app:/app
env_file:
- ./.env
depends_on:
- api
- celery
dashboard:
<<: *api
command: celery --broker=${RABBITMQ_URL} flower --port=5555
ports:
- '25559:5555'
env_file:
- ./.env
depends_on:
- api
- celery
- celery-beat
server {
server_name tools.com
client_max_body_size 100M;
location / {
proxy_pass http://127.0.0.1:8000;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
}
listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/tools.com/fullchain.pem; #
managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/tools.com/privkey.pem; #
managed by Certbot
include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
}
server {
if ($host = tools.com) {
return 301 https://$host$request_uri;
} # managed by Certbot
server_name tools.com
client_max_body_size 100M;
listen 80;
return 404; # managed by Certbot
}
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/49f20832-2433-4f45-adbf-158a0e61a3e0n%40googlegroups.com.