An example from one of my setups:
location /api/deploy/core {
proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_pass http://unix:/applications/deploy/core-api.sock:/;
}
This example is from a CentOS 7.4 box.
On Sun, Sep 16, 2018 at 2:43 PM Bogdan Kulbida <i...@konstankino.com> wrote:
> Hi Ken,
>
> Can you please be more specific on Nginx talking via sockets? Any URLs on
> that topic will be appreciated. Thank you.
>
> On Sun, Sep 16, 2018 at 09:46 Ken M <k...@mack-z.com> wrote:
>
>> On Sun, Sep 16, 2018 at 09:05:33AM +0300, ?????????? ???????????? wrote:
>> > I deploy my django app using uwsgi and venv in my home dir
>> > uWSGi starts on its default port and httpd server uses this port
>> > to handle my app requests. Everything just like in the official manual
>> of
>> > uwsgi.
>> >
>>
>> Don't know if this is helpful for Django apps, or if httpd in openbsd can
>> use
>> unix sockets. Anyway with a couple of falcon api's I setup with Gunicorn I
>> actually used unix sockets instead of creating ports. If my proxy is on
>> the same
>> server as the api's I found that a little easier to manage. Granted in
>> this case
>> it was on centos and I was using nginx. Also in the process of figuring
>> out how
>> to do that I found a lot of the documentation on nginx syntax talking to
>> a unix
>> socket was wrong. But that is another story.
>>
>> Ken
>>
>> --
> ---
> Best regards,
> Bogdan Kulbida
> Founder and CEO, Konstankino LLC <http://konstankino.com>
> +1.802.793.8295
>
>
>
