django - Configuring NGINX for correct URL forwarding to Graphite docker image -


i have web application running on debian through nginx , uwsgi. we've begun using graphite , statsd running in docker container collect stats on application (from https://github.com/hopsoft/docker-graphite-statsd). docker container has own nginx serve graphite. running docker container forwarding port 8081 80 , able access graphite through http:// example.com:8081.

i trying route web traffic graphite through our existing nginx server able use our established authentication method when accessing it.

i able access graphite via example.com/graphite/ , have associated content referred under directory.

currently example.com/graphite/ forwards http:// example.com:8091/graphite/. url not appear change. there, graphite loads up, page elements load :8091/, e.g. http:// example.com:8091/content/js/ext/resources/images/default/sizer/s-handle.gif, whereas referred via http:// example.com/graphite/content/js/ext/resources/images/default/sizer/s-handle.gif.

when go domain.com/graphite/admin/ receive our web application's 404 page. html admin page has loaded successfully, receive 404s https:// example.com/browser/header/ , https:// example.com/composer/?.

here relevant sections of current nginx.conf:

# https server server {     listen                    443;     listen                    8000;     server_name               $hostname;     ssl                       on;     etag                      on;  # used in tests       ssl_verify_client         optional;     ssl_verify_depth          2;       location /graphite {         rewrite                 ^/graphite(/.*)$ $1 break;         proxy_pass              http://localhost:8091;         proxy_set_header        host $host;         proxy_redirect http://127.0.0.1:8091/graphite/ http://$host/graphite/;     }      location /graphite/admin {         rewrite                 ^/graphite(/.*)$ $1 break;         proxy_pass              http://localhost:8091;         proxy_set_header        host $host;         proxy_redirect http://127.0.0.1:8091/graphite/ http://$host/graphite/;     }      location / {         uwsgi_pass              unix:///tmp/web2py.socket;         include                 uwsgi_params;          uwsgi_param             ssl_client_id       $ssl_client_s_dn;         uwsgi_param             remote_user         $ssl_client_s_dn;         uwsgi_param             uwsgi_scheme        $scheme;          #values relay nginx uwsgi         uwsgi_param             ssl_client_cert     $ssl_client_cert;         uwsgi_param             ssl_client_raw_cert $ssl_client_raw_cert;         uwsgi_param             ssl_client_verify   $ssl_client_verify;          uwsgi_param             server_software     nginx/$nginx_version;     }  }   upstream django {     # server unix:///path/to/your/mysite/mysite.sock; # file socket     server 127.0.0.1:8081; # web port socket (we'll use first) }  # graphite server {     listen      8091;     server_name $hostname; # substitute machine's ip address or fqdn     charset     utf-8;     ssl         off;      # max upload size     client_max_body_size 75m;   # adjust taste      location /graphite/ {         proxy_pass http://127.0.0.1:8081/;         proxy_redirect http://127.0.0.1:8081/graphite/ http://$host/graphite/;         proxy_set_header        host $host;         proxy_set_header        script_name /graphite;     }      location / {         proxy_pass http://127.0.0.1:8091/graphite/;     } }

the following /etc/nginx/sites-enabled/graphite-statsd.conf docker image:

server {   listen 80;   root /opt/graphite/webapp/content;   index index.html;    location /media {     # django admin static files     alias /usr/local/lib/python2.7/dist-packages/django/contrib/admin/media/;   }    location /admin/auth/admin {     alias /usr/local/lib/python2.7/dist-packages/django/contrib/admin/static/admin;   }    location /admin/auth/user/admin {     alias /usr/local/lib/python2.7/dist-packages/django/contrib/admin/static/admin;   }    location / {     # checks static file, if not found proxy app     try_files \$uri @app;   }    location @app {     include fastcgi_params;     fastcgi_split_path_info ^()(.*)$;     fastcgi_pass 127.0.0.1:8080;     add_header 'access-control-allow-origin' '*';     add_header 'access-control-allow-methods' 'get, post, options';     add_header 'access-control-allow-headers' 'authorization, content-type';     add_header 'access-control-allow-credentials' 'true';   } }

i pretty new configuring nginx , have never used django before, sure configuration has several problems. appreciated! apologies spaces in urls.


Comments

Post a Comment

Popular posts from this blog

Is there a better way to structure post methods in Class Based Views -

i'm using class based views in django , never specify url in ajax calls , omit action parameter in form because know these requests go through post method of class based view. notice view - profile page make many requests depending on user updating on page - post method become convoluted , if/else mess example: def post(self, request, *args, **kwargs): # handle user changing available date if request.post.get('availabledate') != none: self.updateavailabledate(request) return jsonresponse({'result':'success'}) if request.post.get('newprojectname') != none: creative_user = creativeuserprofile.objects.get(id = request.user.id) project = project.create_project(creative_user, request.post['newprojectname']) project.save() return jsonresponse({'projectid': project.id }) if request.post.get('projectimage') != none , request.files['file']: proj
Read more

performance - Why is XCHG reg, reg a 3 micro-op instruction on modern Intel architectures? -

i'm doing micro-optimization on performance critical part of code , came across sequence of instructions (in at&t syntax): add %rax, %rbx mov %rdx, %rax mov %rbx, %rdx i thought had use case xchg allow me shave instruction , write: add %rbx, %rax xchg %rax, %rdx however, dimay found agner fog's instruction tables , xchg 3 micro-op instruction 2 cycle latency on sandy bridge, ivy bridge, broadwell, haswell , skylake. 3 whole micro-ops , 2 cycles of latency! 3 micro-ops throws off 4-1-1-1 cadence , 2 cycle latency makes worse original in best case since last 2 instructions in original might execute in parallel. now... cpu might breaking instruction micro-ops equivalent to: mov %rax, %tmp mov %rdx, %rax mov %tmp, %rdx where tmp anonymous internal register , suppose last 2 micro-ops run in parallel latency 2 cycles. given register renaming occurs on these micro-architectures, though, doesn't make sense me done way. why wouldn't register renamer
Read more

jquery - Responsive Navbar with Sub Navbar -

good day, forgive me nav vocabulary not best. if question confusing apologize. i'm working on navigation bar needs centered on page @ 768px , above. items in nav open (or perhaps toggle) subnav lives directly below. these nav should appear centered on page. i have been able work through responsive portion of nav bar, having main items align vertically , sub nav menu of each item roll out below, , gave them indent separation. working well. however, issue not responsive side, behavior @ width greater 768px. happens toggling menu's sub navigation pushes other main items down page below sub nav. here's code: $(document).ready(function () { //stick in fixed 100% height behind navbar don't wrap $('#slide-nav.navbar-inverse').after($('<div class="inverse" id="navbar-height-col"></div>')); $('#slide-nav.navbar-default').after($('<div id="navbar-height-col"></d
Read more