I have this docker application running several containers. One of these containers is a Python application that can handle both socket io requests and normal HTTP requests. Django's ASGI handles HTTP/ASGI requests while python-socketio handles socket requests. Since there are…
So my setup is simple. I'm using docker compose to spin up a DB, jBPM and a reverse proxy Nginx service so I can add custom domain and TLS to the equation here. Docker-compose.yml version: '3.8' services: mysql: image: mysql:5.7…
Situation The current (07/2024) docker compose documentation states (falsely) that there is a long-syntax when using 'docker secrets' that can defines the name, uid, gid and mode of the mounted file See example and documentaion: services: frontend: image: example/webapp secrets:…
I am using F5 NGINX Ingress Controller. Note: I am not using Kubernetes community edition ( Ingress-nginx) I have achieved traffic splitting using Virtual server for NGINX Ingress Controller. However in the production some clients are using ip whitelisting and…
I want to authorize the user based on his email without it getting super messy. Is there a better way to do this? http { map $http_user $user { default $http_user; } server { ... location ~ ^(/deployments/).*(xxx).* { set…
I have a combination of Nginx and PHP-FPM, and I want to set the max execution time on the PHP level to be the same as on Nginx. So I add max_execution_time=30 but it does not work. If I create…
I am trying to configure SSL in nginx.conf, and it needs to load the key from softhsm instead of file. Here is the file /etc/nginx/nginx.conf user nginx; worker_processes 1; error_log /var/log/nginx/error.log debug; pid /var/run/nginx.pid; events { worker_connections 1024; } ssl_engine…
Here is my website conf (using nginx v1.25.1): # Redirect to https server { listen 80; server_name domain.name www.domain.name; location ^~ /.well-known/acme-challenge/ { root /acme-challenge; # Make sure this path is correct allow all; } location / { return 301…
My nginx configuration looks like this server { listen 80; server_name host_server; location / { proxy_pass http://localhost:3000; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection 'upgrade'; proxy_set_header Host $host; proxy_cache_bypass $http_upgrade; } location /admin/ { proxy_pass http://localhost:3001; proxy_http_version 1.1; proxy_set_header Upgrade…
This is a very reduced configuration for nginx, which should use different configurations for TLS connections, based on SNI names. Some of them need additional client authentication via client certificates. When I try to configure it, nging -t claims, that…