Live

Provides bi-directional live HTML views using WebSockets for communication. You can try out a live example

Features

Transparent support for both static initial rendering and dynamic updates.
Bi-directional event handling for seamless client/server implementation.
Event-driven architecture for efficient handling of thousands of active connections.

Usage

Please browse the source code index or refer to the guides below.

Getting Started

This guide explains how to use live to render dynamic content in real-time.

Rails Integration

This guide explains how to use the live gem with Ruby on Rails.

Contributing

We welcome contributions to this project.

Fork it.
Create your feature branch (git checkout -b my-new-feature).
Commit your changes (git commit -am 'Add some feature').
Push to the branch (git push origin my-new-feature).
Create new Pull Request.

Developer Certificate of Origin

In order to protect users of this project, we require all contributors to comply with the Developer Certificate of Origin. This ensures that all contributions are properly licensed and attributed.

Community Guidelines

This project is best served by a collaborative and respectful environment. Treat each other professionally, respect differing viewpoints, and engage constructively. Harassment, discrimination, or harmful behavior is not tolerated. Communicate clearly, listen actively, and support one another. If any issues arise, please inform the project maintainers.

Releases

Please browse the releases for more details.

v0.18.0

Breaking Change: Live now uses Web Components for managing life-cycle events instead of observers. You will need to use live-js v0.16.0 or later with this version of live, which emits <live-view> elements (instead of <div> elements).
- Using older versions of live-js with this version of live may result in unexpected behavior or errors.
- Using older versions of live with live-js v0.16.0 or later may also result in unexpected behavior or errors.
Updating both live and live-js to their latest versions is recommended to ensure compatibility, and requires no changes to application code.