Releases: diogob/postgres-websockets
Releases · diogob/postgres-websockets
0.11.2.2
0.11.2.1
0.11.1.0: Add Native TLS connections
- Add TLS native connection so we can have wss:// connections without using any sort of proxy
PGWS_CERTIFICATE_FILE
andPGWS_KEY_FILE
should be used to set the the TLS certificate and enable secure connections.
0.11.0.0: Listener supervisor
- Add PGWS_CHECK_LISTENER_INTERVAL to configure interval to check database listener connection and respawn listener in case the connection is not found.
0.10.0.1: Stack upgrades
- Upgrade stackage to LTS 16.11. Recompiled with GHC 8.8.
- Upgrade Alpine base docker image to Alpine 3.12
0.10.0.0: Meta-data channel
- Add
PGWS_META_CHANNEL
to configure optional metadata channel to send events from the server. Initially the oply event isConnectionOpen
. - Add property
event
to message JSON. Two possible values so far:ConnectionOpen
andWebsocketMessage
. - Breaking change: the property
channel
is not appended to claims anymore. Ifchannel
is in the original token claims it will still be present.
0.9.0.0: New configuration options
- Limit number of retries to connect to database on startup
- Allow use of file to specify database URI
0.8.0.1
0.8.0.0: Multiple Channels
- Added support for opening multiple channels at once and also issue tokens that allow multiple channels - thanks to @jamesmstone
0.7.0.0: Auto-shutdown and auto-closing connections on JWT expiration
- The server
postgres-websockets
will shutdown when the listener database connection is closed, this allows for external process supervisors to restart the service on database failures. - Middleware interface now requires a parameter
IO UTCTime
prividing a function that will produce the system time. - Send close connection once the JWT token expires (if channel is open with a token using the
exp
claim).