Flask+nginx+uwsgi: only serve url with nginx if flask doesn't have a route for it











up vote
1
down vote

favorite












nginx config for the server (the main nginx one is the default one on debian 9):



server {
listen 80;

server_name subdomain.domain.com;
include /etc/nginx/mime.types;
location /galleries {
autoindex on;
alias /srv/galleries/;
}
location / {
include uwsgi_params;
uwsgi_pass unix:/tmp/scraper.sock;
}
}


uwsgi config:



[uwsgi]
module = wsgi:app

master = true
processes = 5

socket = /tmp/scraper.sock
chmod-socket = 777
uid = www-data
gid = www-data
vacuum = true

die-on-term = true
plugins = python3
py-autoreload = 1


If I try creating a route for /galleries/whatever, ie like this:



@app.route("/galleries/whatever")
def test():
return "Hello"


I'll just see the indexed files inside /galleries/whatever through nginx instead of going through flask.



Is there a way for me to force nginx to only handle requests if flask returns 404? Alternatively, is there a better way for me to serve files while still having them available under those urls? Keep in mind the /galleries folder is pretty big and generated by another program.



I run the server with "uwsgi --ini server.ini" and nothing else.










share|improve this question






















  • Maybe using a subdomain name is an idea to overcome this problem?
    – Peshmerge
    Nov 14 at 15:00










  • You mean using a subdomain specifically for the files, having the rest of the path be identical to flask's routes? That's an option, but I was hoping on some simpler solution - I'd like to make my app portable rather than relying on configuring subdomains every time.
    – msaba92
    Nov 14 at 15:44

















up vote
1
down vote

favorite












nginx config for the server (the main nginx one is the default one on debian 9):



server {
listen 80;

server_name subdomain.domain.com;
include /etc/nginx/mime.types;
location /galleries {
autoindex on;
alias /srv/galleries/;
}
location / {
include uwsgi_params;
uwsgi_pass unix:/tmp/scraper.sock;
}
}


uwsgi config:



[uwsgi]
module = wsgi:app

master = true
processes = 5

socket = /tmp/scraper.sock
chmod-socket = 777
uid = www-data
gid = www-data
vacuum = true

die-on-term = true
plugins = python3
py-autoreload = 1


If I try creating a route for /galleries/whatever, ie like this:



@app.route("/galleries/whatever")
def test():
return "Hello"


I'll just see the indexed files inside /galleries/whatever through nginx instead of going through flask.



Is there a way for me to force nginx to only handle requests if flask returns 404? Alternatively, is there a better way for me to serve files while still having them available under those urls? Keep in mind the /galleries folder is pretty big and generated by another program.



I run the server with "uwsgi --ini server.ini" and nothing else.










share|improve this question






















  • Maybe using a subdomain name is an idea to overcome this problem?
    – Peshmerge
    Nov 14 at 15:00










  • You mean using a subdomain specifically for the files, having the rest of the path be identical to flask's routes? That's an option, but I was hoping on some simpler solution - I'd like to make my app portable rather than relying on configuring subdomains every time.
    – msaba92
    Nov 14 at 15:44















up vote
1
down vote

favorite









up vote
1
down vote

favorite











nginx config for the server (the main nginx one is the default one on debian 9):



server {
listen 80;

server_name subdomain.domain.com;
include /etc/nginx/mime.types;
location /galleries {
autoindex on;
alias /srv/galleries/;
}
location / {
include uwsgi_params;
uwsgi_pass unix:/tmp/scraper.sock;
}
}


uwsgi config:



[uwsgi]
module = wsgi:app

master = true
processes = 5

socket = /tmp/scraper.sock
chmod-socket = 777
uid = www-data
gid = www-data
vacuum = true

die-on-term = true
plugins = python3
py-autoreload = 1


If I try creating a route for /galleries/whatever, ie like this:



@app.route("/galleries/whatever")
def test():
return "Hello"


I'll just see the indexed files inside /galleries/whatever through nginx instead of going through flask.



Is there a way for me to force nginx to only handle requests if flask returns 404? Alternatively, is there a better way for me to serve files while still having them available under those urls? Keep in mind the /galleries folder is pretty big and generated by another program.



I run the server with "uwsgi --ini server.ini" and nothing else.










share|improve this question













nginx config for the server (the main nginx one is the default one on debian 9):



server {
listen 80;

server_name subdomain.domain.com;
include /etc/nginx/mime.types;
location /galleries {
autoindex on;
alias /srv/galleries/;
}
location / {
include uwsgi_params;
uwsgi_pass unix:/tmp/scraper.sock;
}
}


uwsgi config:



[uwsgi]
module = wsgi:app

master = true
processes = 5

socket = /tmp/scraper.sock
chmod-socket = 777
uid = www-data
gid = www-data
vacuum = true

die-on-term = true
plugins = python3
py-autoreload = 1


If I try creating a route for /galleries/whatever, ie like this:



@app.route("/galleries/whatever")
def test():
return "Hello"


I'll just see the indexed files inside /galleries/whatever through nginx instead of going through flask.



Is there a way for me to force nginx to only handle requests if flask returns 404? Alternatively, is there a better way for me to serve files while still having them available under those urls? Keep in mind the /galleries folder is pretty big and generated by another program.



I run the server with "uwsgi --ini server.ini" and nothing else.







python nginx flask uwsgi






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 13 at 21:52









msaba92

175110




175110












  • Maybe using a subdomain name is an idea to overcome this problem?
    – Peshmerge
    Nov 14 at 15:00










  • You mean using a subdomain specifically for the files, having the rest of the path be identical to flask's routes? That's an option, but I was hoping on some simpler solution - I'd like to make my app portable rather than relying on configuring subdomains every time.
    – msaba92
    Nov 14 at 15:44




















  • Maybe using a subdomain name is an idea to overcome this problem?
    – Peshmerge
    Nov 14 at 15:00










  • You mean using a subdomain specifically for the files, having the rest of the path be identical to flask's routes? That's an option, but I was hoping on some simpler solution - I'd like to make my app portable rather than relying on configuring subdomains every time.
    – msaba92
    Nov 14 at 15:44


















Maybe using a subdomain name is an idea to overcome this problem?
– Peshmerge
Nov 14 at 15:00




Maybe using a subdomain name is an idea to overcome this problem?
– Peshmerge
Nov 14 at 15:00












You mean using a subdomain specifically for the files, having the rest of the path be identical to flask's routes? That's an option, but I was hoping on some simpler solution - I'd like to make my app portable rather than relying on configuring subdomains every time.
– msaba92
Nov 14 at 15:44






You mean using a subdomain specifically for the files, having the rest of the path be identical to flask's routes? That's an option, but I was hoping on some simpler solution - I'd like to make my app portable rather than relying on configuring subdomains every time.
– msaba92
Nov 14 at 15:44



















active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53290065%2fflasknginxuwsgi-only-serve-url-with-nginx-if-flask-doesnt-have-a-route-for-i%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53290065%2fflasknginxuwsgi-only-serve-url-with-nginx-if-flask-doesnt-have-a-route-for-i%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Biblatex bibliography style without URLs when DOI exists (in Overleaf with Zotero bibliography)

ComboBox Display Member on multiple fields

Is it possible to collect Nectar points via Trainline?