trame-server: server implementation of trame

.. image:: https://github.com/Kitware/trame-server/actions/workflows/test_and_release.yml/badge.svg :target: https://github.com/Kitware/trame-server/actions/workflows/test_and_release.yml :alt: Test and Release

trame-server is the server implementation of trame <https://kitware.github.io/trame/>_. This Python library provide the server implementation of the shared state and controller along with the definition of the web server. The web server aims to be flexible so it can be use within a Jupyter environment or as a standalone desktop application.

This package is not supposed to be used by itself but rather should come as a dependency of trame. For any specificity, please refer to the trame documentation <https://kitware.github.io/trame/>_.

Installing

trame-server can be installed with pip <https://pypi.org/project/trame-server/>_:

.. code-block:: bash

pip install --upgrade trame-server

Usage

The Trame Tutorial <https://kitware.github.io/trame/docs/tutorial.html>_ is the place to go to learn how to use the library and start building your own application.

The API Reference <https://trame.readthedocs.io/en/latest/index.html>_ documentation provides API-level documentation.

Environments variables

• TRAME_LOG_NETWORK : Path to log file for capturing network exchange. (default: None)
• TRAME_WS_MAX_MSG_SIZE : Maximum size in bytes of any ws message. (default: 10MB)
• TRAME_WS_HEART_BEAT : Time in second before assuming the server is non-responsive. (default: 30s)
• TRAME_DESKTOP_DEBUG : If defined it will allow user to inspect the web content in desktop mode
• TRAME_SERVER : If set to true, this will prevent browser from opening by default

Life cycle callbacks

Life cycle events are directly managed on the application controller and are prefixed with on_*.

• on_server_start : Executed at server.start() call while passing the server as argument.

• on_server_bind : WSLinkServer is getting bound to trame so you can attach your own routes. Its instance will be passed as argument to callback.

• on_server_ready : All protocols initialized and available for client to connect

• on_client_connected : Connection established to server

• on_client_exited : Linked to browser "beforeunload" event

• on_server_exited : Trame is exiting its event loop

• on_server_reload : If callback registered it can be use to hot_reload methods like the UI.

License

trame-server is made available under the Apache License, Version 2.0. For more details, see LICENSE <https://github.com/Kitware/trame-server/blob/master/LICENSE>_

Community

Trame <https://kitware.github.io/trame/> | Discussions <https://github.com/Kitware/trame/discussions> | Issues <https://github.com/Kitware/trame/issues> | RoadMap <https://github.com/Kitware/trame/projects/1> | Contact Us <https://www.kitware.com/contact-us/>_

.. image:: https://zenodo.org/badge/410108340.svg :target: https://zenodo.org/badge/latestdoi/410108340

Enjoying trame?

Share your experience with a testimonial <https://github.com/Kitware/trame/issues/18> or with a brand approval <https://github.com/Kitware/trame/issues/19>.