Skip to main content

Server Sent Events (SSE) for Flask using the Mercure protocol

Project description

Flask-Mercure-SSE

Provide push capabilities using server-sent events to your Flask apps. Based on the Mercure protocol.

  • Get started in seconds
  • Full spec implementation
  • Built-in hub
  • Use any external Mercure hub (like the Mercure.rocks hub)

Installation

pip install flask-mercure-sse

Getting started

Enable the MercureSSE extension:

from flask import Flask
from flask_mercure_sse import MercureSSE

app = Flask(__name__)
mercure = MercureSSE(app)

Publish messages from anywhere in your app:

mercure.publish("topic", "message")

Generate subscription urls in your templates:

<script>
const es = new EventSource("{{ mercure_hub_url('topic') }})");
// ...
</script>

Configuration

Key Description Default
MERCURE_HUB_URL External hub url None
MERCURE_PUBLISHER_JWT The authorization JWT to publish on external hubs Required when hub url is provided
MERCURE_AUTHZ_COOKIE_NAME Authorization cookie name mercureAuthorization
MERCURE_TYPE_IS_TOPIC Whether to auto set type to topic name when no type is provided False
MERCURE_HUB_ALLOW_PUBLISH Whether to allow publishing via HTTP with the built-in hub when embedded False
MERCURE_HUB_ALLOW_ANONYMOUS Whether to allow anonymous subscribers to connect True
MERCURE_HUB_SUBSCRIPTIONS Whether to enable the Mercure subscriptions API True
 MERCURE_HUB_KEEPALIVE_INTERVAL Interval in secs between ping messages to ensure the connection is alive, 0 to disable 15
MERCURE_HUB_RECONCILIATION_LENGTH Number of messages to keep across all topics for reconciliation 500
MERCURE_SUBSCRIBER_SECRET_KEY Secret key to generate subscriber JWTs app.config["SECRET_KEY"]
MERCURE_PUBLISHER_SECRET_KEY Secret key to generate publisher JWTs app.config["SECRET_KEY"]

Authorization

Publish privately using private=True in publish().

Use MercureSSE.create_subscription_jwt(topics) or mercure_subscriber_jwt(topics) in templates to generate a JWT. Remember to set a MERCURE_SUBSCRIBER_SECRET_KEY or the app's secret key will be used.

Pass the subscriber JWT to the hub:

  • Use mercure_hub_url(topics, "SUBSCRIBER_JWT") to generate subscription urls with the authorization parameter.
  • Use mercure_authentified_hub_url(topics) to generate subscription urls using a subscriber jwt generated using mercure_subscriber_jwt().
  • Use MercureSSE.set_authz_cookie(response, jwt="SUBSCRIBER_JWT") to define the mercureAuthorization cookie (if jwt is omitted, mercure_subscriber_jwt() is used).

Subscriptions

Track subscriptions using Mercure subscriptions API.

Provide a payload when creating JWTs:

mercure = MercureSSE(app)
@mercure.payload_getter
def get_mercure_payload(topics):
    return {'user_id': current_user.id}

Check whether a subscription exists:

mercure.is_connected(topic, user_id=ID) # keyword arguments are payload filters

List all subscriptions:

subs = mercure.get_subscriptions(topic) # returns the parsed JSON response of the subscriptions endpoint

Built-in hub

The built-in hub can be used in 2 modes:

  • Embedded in your normal flask app. This is for development only as it is not scalable at all.
  • As a standalone server using gevent

It implements the full specification.

In development

First, ensure that a secret key is defined in your app config.

By default, publishing is not possible via the HTTP api for security reasons. You will only be able to publish internally using MercureSSE.publish().

As standalone server

Run the standalone server: python -m flask_mercure_sse.server --subscriber-secret SECRET --publisher-secret SECRET

This will start the server on port 5500. Grab the provided publisher JWT.

In your Flask app, configure the hub:

mercure = MercureSSE(app, hub_url="http://localhost:5500/.well-known/mercure", subscriber_secret_key="SECRET", publisher_jwt="JWT")

Multiplexing a single event source

Set MERCURE_TYPE_IS_TOPIC to true so that events get the same name as the topic they originate from. This allows you to subscribe to multiple topics at once and discriminate messages based on their event name.

Using signals as event sources

Use MercureSSE.publish_signal(signal) to publish an event each time the signal is dispatched

my_event = signal('my-event')
mercure.publish_signal(my_event) # topic is the event name

Check out the parameters of publish_signal() for options when handling the event.

CLI

Some CLI commands are available.

Start with flask mercure --help.

Going to production

Use the built-in hub as a standalone server or use the Mercure.rocks hub in production environments.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

flask_mercure_sse-0.3.0.tar.gz (9.2 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

flask_mercure_sse-0.3.0-py3-none-any.whl (12.0 kB view details)

Uploaded Python 3

File details

Details for the file flask_mercure_sse-0.3.0.tar.gz.

File metadata

  • Download URL: flask_mercure_sse-0.3.0.tar.gz
  • Upload date:
  • Size: 9.2 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: uv/0.8.17

File hashes

Hashes for flask_mercure_sse-0.3.0.tar.gz
Algorithm Hash digest
SHA256 113079599c18d5f48cbdf459b9ef9e87fa00ae08a1c490742479a606baebdaa9
MD5 1c271a6c7fae02e95fa16908a67d6fde
BLAKE2b-256 9cec379eb9033546b0097e36f7f7f2d0ed57edf73f54e49cabbce879257dfdc6

See more details on using hashes here.

File details

Details for the file flask_mercure_sse-0.3.0-py3-none-any.whl.

File metadata

File hashes

Hashes for flask_mercure_sse-0.3.0-py3-none-any.whl
Algorithm Hash digest
SHA256 38eab1cbd1346a359215b9769aac843bf6a100af41aea50a07febc034bbf49aa
MD5 4c3e28049bc3503bb0f7e0640824bc5d
BLAKE2b-256 f76e137f498480c575344f1ead091e2920b1a74f0f5b4c41ede7ecd10c6551c4

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page