Nginx + uwsgi + Flask, Understanding propagation of changes from to deployed stack

Posted February 9, 2018 1k views
Nginx Ubuntu Ubuntu 16.04

Disclaimer & Background:
I am a hobbyist programmer trying to learn how to set up a webserver to host replayable text-logs from a game I play. Every thing I know about coding is self taught via Google/Stack Overflow. I am trying to understand the relationship between deployed nginx+uwsgi+flask so I can continue to solve & maintain what I have written so far.

In short, how do I ensure that changes to .py files that are successfully viewed over the internet served via the virtualenv as well as a cli-run uwsgi can also be successfully viewed over the internet via the defined ip and domain.

I have successfully followed @jtittle1’s step-by-step solve to a basic nginx+uwsgi+flask set up. The basic site sits here.

This works in virtualenv, cli-run uwsgi, by ip and domain.

When I updated my second page (modifying a placeholder), I can successfully view my changes when running the virtualenv as well as the cli-run uwsgi. However, despite restarting the daemonized services and nginx, I am still viewing my placeholder when I navigate to the specified ip and domain.

I have run into an iteration of this problem before where I had to remove (and allow rebuild of) existing .pyc files. I am not sure this is the problem here as I have removed my existing .pyc files and still view the placeholder page. I have viewed this across multiple naive browsers so it is not a cached response.

My question is: if all of my application is represented by the .py files I have since modified, what on earth am I viewing? Abstractly, nginx is serving me a version of my application that is no longer apparently available to me in my application directory. Where and what is this?

Thanks for your patience!

0 answers
Submit an answer

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!