Celery and RQ is overengineering for simple task. Take a look at this docs – https://docs.python.org/3/library/concurrent.futures.html Also check example, how to run long-running jobs in background for Flask app – https://stackoverflow.com/a/39008301/5569578
I’ve recently stumbled upon this need myself and have found that in order to use variables in a proxy_pass destination you need to set a resolver as your error.log would most probably contain something like no resolver defined to resolve … The solution in my case was to setup the following using a local DNS … Read more
Nginx location: Nginx location block section have a search order, a modifier, an implicit match type and an implicit switch to whether stop the search on match or not. the following array describe it for regex. # ——————————————————————————————————————————————– # Search-Order Modifier Description Match-Type Stops-search-on-match # ——————————————————————————————————————————————– # 1st = The URI must match the specified … Read more
This answer might be a bit late, but what you need is an automatic reverse proxy. I have used two solutions for that: jwilder/nginx-proxy Traefik With time, my preference is to use Traefik. Mostly because it is well documented and maintained, and comes with more features (load balancing with different strategies and priorities, healthchecks, circuit … Read more
It depends. Out of the box, putting nginx in front as a reverse proxy is going to give you: Access logs Error logs Easy SSL termination SPDY support gzip support Easy ways to set HTTP headers for certain routes in a couple of lines Very fast static asset serving (if you’re serving off S3/etc. though, … Read more
I think using root in location block is incorrect. I use alias and it works fine, even without re-configuring django. # django settings.py MEDIA_URL = ‘/static/’ # nginx server config server { … location /static { autoindex on; alias /opt/aa/webroot/; } } Hope this makes things simpler.
As stated by Maxim Dounin in the comments above: When nginx returns 400 (Bad Request) it will log the reason into error log, at “info” level. Hence an obvious way to find out what’s going on is to configure error_log to log messages at “info” level and take a look into error log when testing.
I think this will do it for you: location / { try_files /base.html =404; }
You could try upgrading the timeout for your proxy pass in Nginx by adding: proxy_connect_timeout 75s; proxy_read_timeout 300s; on /var/nginx/sites-available/[site-config] or /var/nginx/nginx.conf if you want to increase the timeout limite on all sites served by nginx. You must add –timeout 300 as well to your gunicorn process/config. This solved my problems in the past with … Read more
My comment doesn’t show the whole picture. When I’ve run Django sites on subfolders, I like to use a dynamic config so that you can still access the machine directly (without the proxy) and have a working web-app. This can help a LOT for debugging tricky stuff like this that is hard to reproduce in … Read more