Hi,
Hopefully someone can help me in something that should have a
straightforward solution. I have tried install uwsgi multiple ways,
including pip and apt-get.
This is my ini file inside the vassals subdirectory:
[uwsgi]
chdir = /home/webquest/html/online.webquest.co.nz
uid = webquest
gid = we
Thank you. Changing plugins = python to plugins = python3 seemed to
remove that error but now I am seem to be getting no error but nginx is
saying bad gateway (502 error).
Here is the startup messages in full:
webquest@wagtail1:~/vassals$ uwsgi --emperor ~/vassals/
*** Starting uWSGI 2.0.15-
Turned out to be a socket permission problem. I had to use "chmod-
socket = 666" on the socket. Is working now. :)
On Thu, 2020-03-12 at 12:05 +1300, Glenn Reed wrote:
> Thank you. Changing plugins = python to plugins = python3 seemed to
> remove that error but now I am seem
Hoping someone might be able to advise me
For some reason when I run uwsgi with this script I get no errors:
#!/bin/bash
# Note --http should be used if pointing a browser directly
# to this socket. Otherwise if upstream from nginx use --socket
# Taken from
https://stackoverflow.com/questions/
monize doesn't receive a param, maybe a typo?
>
> However I'd suggest moving the logging flags to your .ini file and
> only
> leave --daemonize in the command call.
>
>
> Cheers
>
> On Mon, Apr 20, 2020 at 03:18:00PM +1200, Glenn Reed wrote:
> > Hoping
Think I solved my own problem.
It was due to not having run collectstatic within Django.
On Tue, 2020-04-21 at 10:04 +1200, Glenn Reed wrote:
> Just to fill in a bit more details I start emperor under a screen
> process. Basically
>
> screen -m uwsgi --emperor ~/vassals
>
>
Dear UWSGI team,
I had a bizarre problem with my Django/Wagtail app running under UWSGI
emperor. The individual sites running as vassals. One in particular
which is probably the single biggest wagtail site we've built to date
has recently run into problems. It revolved around reading a .env file
