You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How can we modify the url route for the flask-profiler? Currently it automatically routes to the main, e.g.
localhost:5000/flask-profiler/
This is fine for debug mode or for production mode where you are not behind a subdomain on a larger server. How can I set the url route for flask-profiler to be behind a subdomain so it works in production mode? E.g. my webapp site is at
We were able to achieve this by setting WSGIScriptAlias in httpd.conf file (service is running inside Tomcat).
WSGIScriptAlias /project-name "/project/path/project-name-rest.wsgi"
How can we modify the url route for the flask-profiler? Currently it automatically routes to the main, e.g.
localhost:5000/flask-profiler/
This is fine for debug mode or for production mode where you are not behind a subdomain on a larger server. How can I set the url route for flask-profiler to be behind a subdomain so it works in production mode? E.g. my webapp site is at
www.domainname.com/myapp/
and I would like to access the flask-profiler at
www.domainname.come/myapp/flask-profiler/
Both of these
fail and do not recognize the name. This question is related to #38.
My config for flask-profiler is configured for production mode
Has anyone actually successfully used this in a production environment and not in debug mode?
The text was updated successfully, but these errors were encountered: