Skip to content

Releases: diogob/postgres-websockets

0.11.2.2

11 Nov 05:41
e58bf5d
Compare
Choose a tag to compare
Add missing upper bounds to test suite

0.11.2.1

06 Oct 22:47
a08194a
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: 0.11.1.0...0.11.2.1

0.11.1.0: Add Native TLS connections

27 Jun 16:14
231c4bd
Compare
Choose a tag to compare
  • Add TLS native connection so we can have wss:// connections without using any sort of proxy PGWS_CERTIFICATE_FILE and PGWS_KEY_FILE should be used to set the the TLS certificate and enable secure connections.

0.11.0.0: Listener supervisor

17 Jun 03:59
9d24940
Compare
Choose a tag to compare
  • 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

23 Oct 05:08
a1571a5
Compare
Choose a tag to compare
  • 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

16 Oct 21:43
995683e
Compare
Choose a tag to compare
  • Add PGWS_META_CHANNEL to configure optional metadata channel to send events from the server. Initially the oply event is ConnectionOpen.
  • Add property event to message JSON. Two possible values so far: ConnectionOpen and WebsocketMessage.
  • Breaking change: the property channel is not appended to claims anymore. If channel is in the original token claims it will still be present.

0.9.0.0: New configuration options

10 Sep 23:56
9f2cfc4
Compare
Choose a tag to compare
  • Limit number of retries to connect to database on startup
  • Allow use of file to specify database URI

0.8.0.1

11 Aug 23:38
27b0c24
Compare
Choose a tag to compare
Fix version bounds on protolude to avoid error when compiling with 0.3

0.8.0.0: Multiple Channels

11 Aug 17:56
39f2515
Compare
Choose a tag to compare
  • 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

12 Jun 03:26
4abcd12
Compare
Choose a tag to compare
  • 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).