-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for UNIX sockets #7
Comments
Ok, I wrote a small patch, it's committed in badlop@35550c5 And the corresponding update in ejabberd is badlop/ejabberd@b90e7fa With that, sql_server: "unix:/var/run/postgresql/.s.PGSQL.5432" It worked for me, please give it a try. If you need binary installers or containers for testing, tell me. |
Wow @badlop 🥇! Amazing response time here. As I had never run ejabberd from source before it took my an hour to get it running as I wanted to help out testing. But then I got it to run successfully using both the old TCP/IP and new UNIX domain socket connection for PostgreSQL. NOTE: I just did a smoke test and my conversejs is happy with either server 👍 . |
Thank you very much for this @badlop , that is Awesome! @jeroenhabets did you keep any notes for compiling/running from source? My instance of ejabberd is installed from a .deb file. |
@Jieiku I did :) My starting point was: For the tests I did:
Hope this is of any help to you... |
This was committed in 996001d, and will be available in the next p1_pgsql release. |
As per processone/ejabberd#3716 (comment) this library lacks support for UNIX sockets, thus blocking adding PostgreSQL UNIX socket support to ejabberd (also requested in processone/ejabberd#3165).
Now that Erlang has (stable) UNIX socket support for a while, a.o. used by ejabberd itself, it should be feasible.
The text was updated successfully, but these errors were encountered: