|
I'm running a Flask app via supervisor which is running on its own custom web app. The supervisor script works fine – runs flask, can restart from the command line fine, etc. The problem is the supervisor admin page cannot find any of its static files. This would be fine as I don't really care about the aesthetics of the admin page for this project but it is also causing the the buttons such as restart, stop, clear, etc to be unusable. Again this isn't the worst thing in the world, I can restart the app through the command line but I will be handing this project over and would like for them to be able to restart the app without needing to ssh and type in the commands. When I first got supervisor running the static files were properly linked. Since installing supervisor I have manually killed some processes which I think may be the cause of my problem. I'm just not sure what I would run to get these static files linked again. Thanks! asked 28 Mar '16, 18:21 Matt Visco |
|
It sounds to me like you're running supervisor on a URL path below the root. This means that the front end Nginx server will get requests for (for example) yourdomain.com/supervisor and proxy them to supervisor on the back end. The problem is that supervisor itself does not know that it's running on /supervisor, so it's generating all of its own URLs as though it were running on the root. I've checked the supervisor documentation, and I don't see any obvious way to configure supervisor to recognize when it is running from a URL below the root, so my advice is that you run it from the root of a separate site on a separate subdomain, like supervisor.yourdomain.com. answered 28 Mar '16, 18:32 seanf Cool - makes sense, that fixed it!
(28 Mar '16, 18:52)
Matt Visco
|
