Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 16 Aug 2017 12:26:47 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-ports-bugs@FreeBSD.org
Subject:   [Bug 210170] www/uwsgi: Add Emperor mode support
Message-ID:  <bug-210170-13-QzHe2nPjSl@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-210170-13@https.bugs.freebsd.org/bugzilla/>
References:  <bug-210170-13@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210170

--- Comment #14 from David Wahlund <david@dafnet.se> ---
* 165:165 seems to be the reserved uwsgi uid/gid since jan
https://reviews.freebsd.org/D9398. As I'm using --chown-socket to specify
uid:gid I'm sure what the uid:gid is. However, it seems a good idea to user
uwsgi:www instead. Making sure uwsgi has rw to socket after it has dropped =
to
the uwsgi user. This seems to have been solved previously by running uwsgi =
as
www:www. Pretty sure that's not a good idea. Also it shouldn't break anythi=
ng
on update.

* I've found a problem with flags though. Current installations, I think
(atleast I am), uses the uwsgi_flags to pass the config-file argument. This
overwrites the default flags (-M -L). Seems to be impossible to pass a conf=
ig
file without overwriting them. Seems to work based on the only argument pas=
sed
not being a flag is intepreted as a config file. So the actual command is n=
ow
'uwsgi <path to config> <lots of flags passed as args>', not pretty. Maybe =
put
an update notice on using the new uwsgi_configfile instead. This is limited=
 to
ini-format right now even though uwsgi supports multiple formats. Adding
uwsgi_configfile_json etc might be an idea for the future.

I reworked the flags handling a bit and now I'm using the start_precmd() to=
 set
rc_flags and then concating the uwsgi_flags at the end of it. This will work
with existing rc.conf settings using uwsgi_flags to specify conf-file.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-210170-13-QzHe2nPjSl>