Does this work with the mobile apps?

Does this work with the mobile apps?

Yes. does not affect mobile apps. I use both PWA and Android mobile app.

@balki Does the PWA now connect via the socket? Or how you want to use the socket since AFAIK it works only locally.

@JBlond @advplyr

AFAIK it works only locally.

Yes. right sockets work locally only. You need a web server like Caddy / Nginx / Apache that connects to audiobookshelf over unix socket. E.g. I have below in my caddy config.

audiobookshelf.mydomain.com {
    log {
        output file /var/log/caddy/audiobookshelf.log
    }
    header {
        Content-Security-Policy "default-src 'self' 'unsafe-inline' data: blob:;"
        Referrer-Policy same-origin
    }
    reverse_proxy unix//run/audiobookshelf/web.sock
}

The reverse_proxy line above is the path to the unix socket.

I use audiobookshelf installed on archlinux: package which uses environment variables for configuration.

I have set the environment variable HOST=unix//run/audiobookshelf/web.sock. With this PR, audiobookshelf listens on the unix socket at that path.

Both PWA and android app, connects to https://audiobookshelf.mydomain.com which is served by caddy web server. They don't know/care that the web server internally connects to audiobookshelf via unix socket.

@advplyr It would be very helpful to have this feature merged soon. I have been patching and manually compiling audiobookshelf for past few releases now to get this support.

I run all my selfhosted applications listening via unix sockets so that they can be isolated into dedicated network namespaces.

This is a common feature and supported by most self-hosted applications. Few examples:

Also the change is small, straightforward and does not add any new configuration.
Absolutely no side-effect for users who don't use the feature.