gunicorn

I am trying to restrict access to the admin section of my django app by using simple host-based access control in nginx. Unfortunately nginx does not seem to abide by the configuration request: this is my setting for this particular section in nginx: # gunicorn setup 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; } location /admin/ { # restrict access to admin section allow 192.168.0.1; deny all; } This does still block my ip 192.168.0.1. What am I doing wrong? Is

The setup is as follows: I have a Gunicorn/Django app running on 0.0.0.0:8000 that is accessible via the browser. To serve static files I am running nginx as a reverse proxy. /etc/nginx/nginx.conf is configured to forward requests as follows: server { location /static/ { alias /data/www/; } # Proxying the connections location / { proxy_set_header Host $host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_redirect off; proxy_pass http://0.0.0.0:8000; } } and my docker-compose.yml file is as follows: version: '3.3' services: web: restart: always build: ./web expose: - "8000"

I want to serve a flask app that uses embedded bokeh serve from a server on my local network. To illustrate I made an example using the bokeh serve example and a docker image to replicate the server. The docker image runs Nginx and Gunicorn. I think there is a problem with my nginx configuration routing the requests to the /bkapp uri. I have detailed the problem and provided all source code in the following git repo I have started a discussion on bokeh google group Single Container In order to reduce the complexity of running nginx in its own container I built this image that runs nginx in

I have Ubuntu+NGINX+Gunicorn with a virtual environment that works with Python 3 setup but my Flask app still runs as 2.7.6. I have methodically followed the instructions but I cannot find a resolution. Gunicorn config file [program:app-server] command = gunicorn app:app -b localhost:8000 directory = /home/www/app-server user = appuser Project directory structure app-server ----app.py ----venv (virtual environment) Gunicorn is itself a Python application; the Gunicorn PPA only publishes Python 2 versions. You'd install Gunicorn into Python 3 instead (using pip , preferably into your virtualenv

I git cloned a project in my home folder, let's call it /home/telessaude . So the project root is located at /home/telessaude/telessaude_branch_master If I am inside the Django project home folder ( /home/telessaude/telessaude_branch_master ) and issue a gunicorn comman such as gunicorn -w 2 -b 0.0.0.0:8000 telessaude.wsgi_dev:application --reload --timeout 900 gunicorn starts and works just fine. However ... if I try to run the same command on one directory above ( /home/telessaude ), I get the following error: telessaude@ubuntu:~$ gunicorn -w 2 -b 0.0.0.0:8000 telessaude.wsgi_dev:application

I am trying to run Gunicorn from Supervisor in an Ubuntu 12.04 system. Gunicorn runs a Flask app (simple REST web service tested with Flask's embedded server). I have installed Gunicorn by clonning GIT repo, trying to avoid 'apt-get install' because it runs Gunicorn server when installs it. I do not want it running, it will be run by Supervisor only. So after install it, if I try: cd /usr/local/bin gunicorn my_app:app -c /path/to/gu_config_file Gunicorn works. Then I kill it. Note config file without extension, because with '.py' extension does not work for me. So I edit Supervisor's config

I have made a django web app using the default localhost, however I am trying to set it up on a server so that I can configure a postgre database and continue on without having to redo the database later on. I am hosting the site though a digital ocean ubuntu 14 droplet. When I created the droplet I selected that it already come preconfigured for django. It uses nginx and gunicorn to host the site. When I first created the instance of the server, a basic django app was configured to work on the given IP. And it did. I tried cloning my project into the same directory as that project assuming it