All Versions
14
Latest Version
Avg Release Cycle
58 days
Latest Release
-
Changelog History
Page 1
Changelog History
Page 1
-
v0.11.2.0 Changes
- โฌ๏ธ Upgrade stackage to LTS 19.0. Recompiled with GHC 9.0.2.
- ๐ Change code so we can use aeson's LTS 19.0 version (2.0.3.0).
-
v0.11.1.0 Changes
- Add TLS native connection so we can have
wss://
connections without using any sort of proxyPGWS_CERTIFICATE_FILE
andPGWS_KEY_FILE
should be used to set the the TLS certificate and enable secure connections.
- Add TLS native connection so we can have
-
v0.11.0.0 Changes
- Add
PGWS_CHECK_LISTENER_INTERVAL
to configure interval to check database listener connection and respawn listener in case the connection is not found.
- Add
-
v0.10.0.1 Changes
October 23, 2020- โฌ๏ธ Upgrade stackage to LTS 16.11. Recompiled with GHC 8.8.3.
- โฌ๏ธ Upgrade Alpine base docker image to Alpine 3.12
-
v0.10.0.0 Changes
October 16, 2020- 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.
- Add
-
v0.9.0.0 Changes
September 10, 2020- Add @filename semantics to PGWS_DB_URI configiration variable to allow secret management to use a file instead of an environment variable.
- โ Add
PGWS_RETRIES
to limit the amount of times the server tries to open a database connection upon startup (defaults to 5). This breaks backward compatibility if you rely on the behaviour of the server to try infitite times.
-
v0.8.0.1 Changes
August 11, 2020- ๐ Fix compilation error due to missing version upper bound for protolude.
-
v0.8.0.0 Changes
August 11, 2020- โ Added support for opening multiple channels at once and also issue tokens that allow multiple channels - thanks to @jamesmstone
-
v0.7.0.0 Changes
June 12, 2020- 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).
- The server
-
v0.6.1.1
May 29, 2020