-
Notifications
You must be signed in to change notification settings - Fork 7
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
event port #3
Comments
I didn't test this feature, but I don't see any reason why it should not work. Just use |
That should work, but would it better to provide a working configuration out of the box? |
Suggestions? |
Set a default port, perhaps 3051, in the firebird.conf and EXPOSE it? |
For a rarely used feature, and one that the Also, the lack of a standardized port. |
If not in the base image, then an example config in the README at least? Only because it will be quite confusing for users who do use events when they don't work. |
Will events work with Firebird running inside the container? I didn't try it, but I suspect not. Firebird randomly allocates the port and as it isn't mapped/exposed to the host, clients won't be able to connect. I think the solution is to configure a fixed port and expose that also.
The text was updated successfully, but these errors were encountered: