Skip to content

"Melbourne": WSGI with Gunicorn - why cant change to socket vs sock everywhere? #58

@erjan

Description

@erjan

i need clarification here - should the name "gunicorn.sock" be hardcoded? or can it be "gunicorn.socket"?

i changed its name in gunicorn configs at /etc/systemd/system/gunicorn.service

yet when i restart gunicorn service - it still shows its listening on "sock" not socket

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions