I figured it out. Before cloning the site I had upgraded from 3.1 to 3.2.
After the upgrade I had stopped and restarted nginx, but I had not bounced
the uwsgi daemon which was caching the older version of Django (not the
first time I've been bitten by that, so shame on me, I have no excuse ).
A few more data points:
- no errors are shown in the browser's developer tools console for
either instance of the site
- no resources are shown as having failed to load in the browser's
developer tools network tab
- no errors are logged by either web server
--
You received this
I have a Django site I've been running for years (since before the 1.x
days). Right now it's running 3.2 and I have "cloned" it to another Ubuntu
20.4 server so that I can test the upgrade to 4.x. The cloning process
involved:
- pushing the site's code to a private GitHub repo
- git
3 matches
Mail list logo
