Package: zenoh-plugin-webserver
Version: 1.0.0~rc.1-1
Architecture: armel
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 10194
Depends: zenohd (=1.0.0~rc.1-1)
Filename: 1.0.0-rc.1/zenoh-plugin-webserver_1.0.0~rc.1-1_armel.deb
Size: 2144200
MD5sum: 64ddf57fddf56985e2def3898847884f
SHA1: ac41bfaa92ec67291c8cff463374295d782c4ea3
SHA256: 3af88b5594b54239ce1fca82c4f858f2a4ccdd2596fad0786c155102693aa99e
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: Plugin for Zenoh implementing an HTTP server that maps URLs to zenoh key
expressions
.
[](https://github.com/eclipse-zenoh/zenoh-plugin-webserver/actions?query=workflow%3A%22CI%22)
[](https://github.com/eclipse-zenoh/roadmap/discussions)
[](https://discord.gg/2GJ958VuHs)
[](https://choosealicense.com/licenses/epl-2.0/)
[](https://opensource.org/licenses/Apache-2.0)
.
# Eclipse Zenoh
The Eclipse Zenoh: Zero Overhead Pub/sub, Store/Query and Compute.
.
Zenoh (pronounce _/zeno/_) unifies data in motion, data at rest and
computations. It carefully blends traditional pub/sub with geo-distributed
storages, queries and computations, while retaining a level of time and space
efficiency that is well beyond any of the mainstream stacks.
.
Check the website [zenoh.io](http://zenoh.io) and the
[roadmap](https://github.com/eclipse-zenoh/roadmap) for more detailed
information.
.
-------------------------------
# Web Server plugin
.
The Web Server plugin implements an HTTP server mapping URLs to zenoh keys.
This plugin can be used to set-up a Web server where the resources are
retrieved from geo-distributed
zenoh storages, each leveraging various backends (file system, database,
memory...).
.
**Library name** `zenoh_plugin_webserver`
.
:point_right: **Download stable versions:**
https://download.eclipse.org/zenoh/zenoh-plugin-webserver/
.
:point_right: **Build "main" branch:** see [below](#How-to-build-it)
.
-------------------------------
## :warning: Documentation for previous 0.5 versions:
The following documentation related to the version currently in development in
"main" branch: 0.6.x.
.
For previous versions see the README and code of the corresponding tagged
version:
-
[0.5.0-beta.9](https://github.com/eclipse-zenoh/zenoh-plugin-webserver/tree/0.5.0-beta.9#readme)
-
[0.5.0-beta.8](https://github.com/eclipse-zenoh/zenoh-plugin-webserver/tree/0.5.0-beta.8#readme)
.
-------------------------------
## **Examples of usage**
.
Assuming you have a static website, you can:
- expose the files as zenoh key/values using the [File System
backend](https://github.com/eclipse-zenoh/zenoh-backend-filesystem)
- set-up this Web Server plugin that will allow HTTP clients to browse the
files.
.
Here are the steps:
1. Make sure the libraries for the File System backend and the Web Server
plugin are available for the zenoh router:
either installing their packages (depending your platform), either
downloading the library files corresponding
to your platform in your `~/.zenoh/lib` directory.
2. Copy the website files into a `~/.zenoh/zbackend_fs/my-site` directory (or
make it a symbolic link to the path of your website)
3. Create a `zenoh.json5` configuration file containing:
```json5
{
plugins: {
webserver: {
http_port: 8080,
},
storage_manager: {
volumes: {
fs: {}
},
storages: {
demo: {
key_expr: "my-site/**",
strip_prefix: "my-site",
volume: {
id: "fs",
dir: "my-site",
read_only: true
}
}
}
}
}
}
```
4. Start the zenoh router (`zenohd`). It will automatically load the Web
Server plugin and make it available on port 8080. It will also create a storage
replying to any zenoh query on key expressions starting with `my-site/`.
Now you can browse your site on http://localhost:8080/my-site.
.
.
For more advanced use cases you can also:
- Have the files of your web sites stored on different hosts. Running a zenoh
router with a File System Storage on
each host allow to make all the files available under the `my-site/` zenoh
key.
- Duplicate the files of your web sites on several hosts to provide fault
tolerance.
- Start several zenoh routers with the Web Service plugin on different hosts
(not necessarly the same than the
hosts running the File System storages). Each host will serve your web site.
- Use other backends than the File System to store your resources and make
them available through zenoh.
(List of available backends
[here](http://zenoh.io/docs/manual/backends-list/)).
- Deploy a zenoh application that will implement `eval` function for a
resource, replying to requests with a
dynamic content (see the `z_eval` example in
[Rust](https://github.com/eclipse-zenoh/zenoh/blob/main/zenoh/examples/zenoh/z_eval.rs)
or
[Python](https://github.com/eclipse-zenoh/zenoh-python/blob/main/examples/zenoh/z_eval.py)).
.
-------------------------------
## **Configuration**
.
In its configuration part, the plugin supports those settings:
- **`http_port`** - int or string - required:
either a port number as an integer or a string, either a string with format
`":"`
.
-------------------------------
## **Troubleshooting**
.
### *Address already in use*
If in `zenohd` logs you see such error log at startup:
```
[2021-04-12T14:20:51Z ERROR zenoh_plugin_webserver] Unable to start http server
for REST : Os { code: 48, kind: AddrInUse, message: "Address already in use" }
```
It means another process is already using this port number that the webserver
plugin would like to use.
In such case, you have 2 solutions:
- stop the other process using this port
- make the webserver plugin to another port changing its `listener` option.
.
### *Permission denied*
If in `zenohd` logs you see such error log at startup:
```
[2021-04-12T13:55:10Z ERROR zenoh_plugin_webserver] Unable to start http server
for REST : Os { code: 13, kind: PermissionDenied, message: "Permission denied"
```
It probably means your OS (this usually happens on Linux) forbids the usage of
the configured port for non-root user (actually it usually restricts all ports
between 0 and 1024).
In such case, you have 2 solutions:
- run zenohd with root privileges (via `sudo`)
- use another changing he webserver plugin's `listener` option.
.
-------------------------------
## **How to build it**
.
> :warning: **WARNING** :warning: : Zenoh and its ecosystem are under active
development. When you build from git, make sure you also build from git any
other Zenoh repository you plan to use (e.g. binding, plugin, backend, etc.).
It may happen that some changes in git are not compatible with the most recent
packaged Zenoh release (e.g. deb, docker, pip). We put particular effort in
mantaining compatibility between the various git repositories in the Zenoh
project.
.
> :warning: **WARNING** :warning: : As Rust doesn't have a stable ABI, the
plugins should be
built with the exact same Rust version than `zenohd`, and using for `zenoh`
dependency the same version (or commit number) than 'zenohd'.
Otherwise, incompatibilities in memory mapping of shared types between `zenohd`
and the library can lead to a `"SIGSEV"` crash.
.
At first, install [Cargo and
Rust](https://doc.rust-lang.org/cargo/getting-started/installation.html). If
you already have the Rust toolchain installed, make sure it is up-to-date with:
.
```bash
$ rustup update
```
.
To know the Rust version you're `zenohd` has been built with, use the
`--version` option.
Example:
```bash
$ zenohd --version
The zenoh router v0.6.0-beta.1 built with rustc 1.64.0 (a55dd71d5 2022-09-19)
```
Here, `zenohd` has been built with the rustc version `1.64.0`.
Install and use this toolchain with the following command:
.
```bash
$ rustup default 1.64.0
```
.
And `zenohd` version corresponds to an un-released commit with id `1f20c86`.
Update the `zenoh` dependency in Cargo.lock with this command:
```bash
$ cargo update -p zenoh --precise 1f20c86
```
.
Then build the backend with:
```bash
$ cargo build --release -p zenoh-plugin-webserver
```
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh-plugin-webserver
Vcs-Git: https://github.com/eclipse-zenoh/zenoh-plugin-webserver
Package: zenoh-plugin-webserver
Version: 1.0.0~rc.1-1
Architecture: arm64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 12453
Depends: zenohd (=1.0.0~rc.1-1)
Filename: 1.0.0-rc.1/zenoh-plugin-webserver_1.0.0~rc.1-1_arm64.deb
Size: 2343744
MD5sum: e7913c0bca1e55311e84dff3ebb62eb1
SHA1: 2e954c55c94783a9b73560f1565bff6306d3baaf
SHA256: 610f159af94ee735b2eecfa0fb1255a523d11988259b5eb7bfd0ab921ae35017
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: Plugin for Zenoh implementing an HTTP server that maps URLs to zenoh key
expressions
.
[](https://github.com/eclipse-zenoh/zenoh-plugin-webserver/actions?query=workflow%3A%22CI%22)
[](https://github.com/eclipse-zenoh/roadmap/discussions)
[](https://discord.gg/2GJ958VuHs)
[](https://choosealicense.com/licenses/epl-2.0/)
[](https://opensource.org/licenses/Apache-2.0)
.
# Eclipse Zenoh
The Eclipse Zenoh: Zero Overhead Pub/sub, Store/Query and Compute.
.
Zenoh (pronounce _/zeno/_) unifies data in motion, data at rest and
computations. It carefully blends traditional pub/sub with geo-distributed
storages, queries and computations, while retaining a level of time and space
efficiency that is well beyond any of the mainstream stacks.
.
Check the website [zenoh.io](http://zenoh.io) and the
[roadmap](https://github.com/eclipse-zenoh/roadmap) for more detailed
information.
.
-------------------------------
# Web Server plugin
.
The Web Server plugin implements an HTTP server mapping URLs to zenoh keys.
This plugin can be used to set-up a Web server where the resources are
retrieved from geo-distributed
zenoh storages, each leveraging various backends (file system, database,
memory...).
.
**Library name** `zenoh_plugin_webserver`
.
:point_right: **Download stable versions:**
https://download.eclipse.org/zenoh/zenoh-plugin-webserver/
.
:point_right: **Build "main" branch:** see [below](#How-to-build-it)
.
-------------------------------
## :warning: Documentation for previous 0.5 versions:
The following documentation related to the version currently in development in
"main" branch: 0.6.x.
.
For previous versions see the README and code of the corresponding tagged
version:
-
[0.5.0-beta.9](https://github.com/eclipse-zenoh/zenoh-plugin-webserver/tree/0.5.0-beta.9#readme)
-
[0.5.0-beta.8](https://github.com/eclipse-zenoh/zenoh-plugin-webserver/tree/0.5.0-beta.8#readme)
.
-------------------------------
## **Examples of usage**
.
Assuming you have a static website, you can:
- expose the files as zenoh key/values using the [File System
backend](https://github.com/eclipse-zenoh/zenoh-backend-filesystem)
- set-up this Web Server plugin that will allow HTTP clients to browse the
files.
.
Here are the steps:
1. Make sure the libraries for the File System backend and the Web Server
plugin are available for the zenoh router:
either installing their packages (depending your platform), either
downloading the library files corresponding
to your platform in your `~/.zenoh/lib` directory.
2. Copy the website files into a `~/.zenoh/zbackend_fs/my-site` directory (or
make it a symbolic link to the path of your website)
3. Create a `zenoh.json5` configuration file containing:
```json5
{
plugins: {
webserver: {
http_port: 8080,
},
storage_manager: {
volumes: {
fs: {}
},
storages: {
demo: {
key_expr: "my-site/**",
strip_prefix: "my-site",
volume: {
id: "fs",
dir: "my-site",
read_only: true
}
}
}
}
}
}
```
4. Start the zenoh router (`zenohd`). It will automatically load the Web
Server plugin and make it available on port 8080. It will also create a storage
replying to any zenoh query on key expressions starting with `my-site/`.
Now you can browse your site on http://localhost:8080/my-site.
.
.
For more advanced use cases you can also:
- Have the files of your web sites stored on different hosts. Running a zenoh
router with a File System Storage on
each host allow to make all the files available under the `my-site/` zenoh
key.
- Duplicate the files of your web sites on several hosts to provide fault
tolerance.
- Start several zenoh routers with the Web Service plugin on different hosts
(not necessarly the same than the
hosts running the File System storages). Each host will serve your web site.
- Use other backends than the File System to store your resources and make
them available through zenoh.
(List of available backends
[here](http://zenoh.io/docs/manual/backends-list/)).
- Deploy a zenoh application that will implement `eval` function for a
resource, replying to requests with a
dynamic content (see the `z_eval` example in
[Rust](https://github.com/eclipse-zenoh/zenoh/blob/main/zenoh/examples/zenoh/z_eval.rs)
or
[Python](https://github.com/eclipse-zenoh/zenoh-python/blob/main/examples/zenoh/z_eval.py)).
.
-------------------------------
## **Configuration**
.
In its configuration part, the plugin supports those settings:
- **`http_port`** - int or string - required:
either a port number as an integer or a string, either a string with format
`":"`
.
-------------------------------
## **Troubleshooting**
.
### *Address already in use*
If in `zenohd` logs you see such error log at startup:
```
[2021-04-12T14:20:51Z ERROR zenoh_plugin_webserver] Unable to start http server
for REST : Os { code: 48, kind: AddrInUse, message: "Address already in use" }
```
It means another process is already using this port number that the webserver
plugin would like to use.
In such case, you have 2 solutions:
- stop the other process using this port
- make the webserver plugin to another port changing its `listener` option.
.
### *Permission denied*
If in `zenohd` logs you see such error log at startup:
```
[2021-04-12T13:55:10Z ERROR zenoh_plugin_webserver] Unable to start http server
for REST : Os { code: 13, kind: PermissionDenied, message: "Permission denied"
```
It probably means your OS (this usually happens on Linux) forbids the usage of
the configured port for non-root user (actually it usually restricts all ports
between 0 and 1024).
In such case, you have 2 solutions:
- run zenohd with root privileges (via `sudo`)
- use another changing he webserver plugin's `listener` option.
.
-------------------------------
## **How to build it**
.
> :warning: **WARNING** :warning: : Zenoh and its ecosystem are under active
development. When you build from git, make sure you also build from git any
other Zenoh repository you plan to use (e.g. binding, plugin, backend, etc.).
It may happen that some changes in git are not compatible with the most recent
packaged Zenoh release (e.g. deb, docker, pip). We put particular effort in
mantaining compatibility between the various git repositories in the Zenoh
project.
.
> :warning: **WARNING** :warning: : As Rust doesn't have a stable ABI, the
plugins should be
built with the exact same Rust version than `zenohd`, and using for `zenoh`
dependency the same version (or commit number) than 'zenohd'.
Otherwise, incompatibilities in memory mapping of shared types between `zenohd`
and the library can lead to a `"SIGSEV"` crash.
.
At first, install [Cargo and
Rust](https://doc.rust-lang.org/cargo/getting-started/installation.html). If
you already have the Rust toolchain installed, make sure it is up-to-date with:
.
```bash
$ rustup update
```
.
To know the Rust version you're `zenohd` has been built with, use the
`--version` option.
Example:
```bash
$ zenohd --version
The zenoh router v0.6.0-beta.1 built with rustc 1.64.0 (a55dd71d5 2022-09-19)
```
Here, `zenohd` has been built with the rustc version `1.64.0`.
Install and use this toolchain with the following command:
.
```bash
$ rustup default 1.64.0
```
.
And `zenohd` version corresponds to an un-released commit with id `1f20c86`.
Update the `zenoh` dependency in Cargo.lock with this command:
```bash
$ cargo update -p zenoh --precise 1f20c86
```
.
Then build the backend with:
```bash
$ cargo build --release -p zenoh-plugin-webserver
```
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh-plugin-webserver
Vcs-Git: https://github.com/eclipse-zenoh/zenoh-plugin-webserver
Package: zenoh-plugin-webserver
Version: 1.0.0~rc.1-1
Architecture: amd64
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 13305
Depends: zenohd (=1.0.0~rc.1-1)
Filename: 1.0.0-rc.1/zenoh-plugin-webserver_1.0.0~rc.1-1_amd64.deb
Size: 2518768
MD5sum: ec7bad2db1a01f68e05085b87c74e7f1
SHA1: 39bd20470f76f86f4aa1990733a73b3ecb609188
SHA256: 128cced1f29cc1457f0b4a617509b9d3d08a0deefa722a7c53a3e06f3e21fa07
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: Plugin for Zenoh implementing an HTTP server that maps URLs to zenoh key
expressions
.
[](https://github.com/eclipse-zenoh/zenoh-plugin-webserver/actions?query=workflow%3A%22CI%22)
[](https://github.com/eclipse-zenoh/roadmap/discussions)
[](https://discord.gg/2GJ958VuHs)
[](https://choosealicense.com/licenses/epl-2.0/)
[](https://opensource.org/licenses/Apache-2.0)
.
# Eclipse Zenoh
The Eclipse Zenoh: Zero Overhead Pub/sub, Store/Query and Compute.
.
Zenoh (pronounce _/zeno/_) unifies data in motion, data at rest and
computations. It carefully blends traditional pub/sub with geo-distributed
storages, queries and computations, while retaining a level of time and space
efficiency that is well beyond any of the mainstream stacks.
.
Check the website [zenoh.io](http://zenoh.io) and the
[roadmap](https://github.com/eclipse-zenoh/roadmap) for more detailed
information.
.
-------------------------------
# Web Server plugin
.
The Web Server plugin implements an HTTP server mapping URLs to zenoh keys.
This plugin can be used to set-up a Web server where the resources are
retrieved from geo-distributed
zenoh storages, each leveraging various backends (file system, database,
memory...).
.
**Library name** `zenoh_plugin_webserver`
.
:point_right: **Download stable versions:**
https://download.eclipse.org/zenoh/zenoh-plugin-webserver/
.
:point_right: **Build "main" branch:** see [below](#How-to-build-it)
.
-------------------------------
## :warning: Documentation for previous 0.5 versions:
The following documentation related to the version currently in development in
"main" branch: 0.6.x.
.
For previous versions see the README and code of the corresponding tagged
version:
-
[0.5.0-beta.9](https://github.com/eclipse-zenoh/zenoh-plugin-webserver/tree/0.5.0-beta.9#readme)
-
[0.5.0-beta.8](https://github.com/eclipse-zenoh/zenoh-plugin-webserver/tree/0.5.0-beta.8#readme)
.
-------------------------------
## **Examples of usage**
.
Assuming you have a static website, you can:
- expose the files as zenoh key/values using the [File System
backend](https://github.com/eclipse-zenoh/zenoh-backend-filesystem)
- set-up this Web Server plugin that will allow HTTP clients to browse the
files.
.
Here are the steps:
1. Make sure the libraries for the File System backend and the Web Server
plugin are available for the zenoh router:
either installing their packages (depending your platform), either
downloading the library files corresponding
to your platform in your `~/.zenoh/lib` directory.
2. Copy the website files into a `~/.zenoh/zbackend_fs/my-site` directory (or
make it a symbolic link to the path of your website)
3. Create a `zenoh.json5` configuration file containing:
```json5
{
plugins: {
webserver: {
http_port: 8080,
},
storage_manager: {
volumes: {
fs: {}
},
storages: {
demo: {
key_expr: "my-site/**",
strip_prefix: "my-site",
volume: {
id: "fs",
dir: "my-site",
read_only: true
}
}
}
}
}
}
```
4. Start the zenoh router (`zenohd`). It will automatically load the Web
Server plugin and make it available on port 8080. It will also create a storage
replying to any zenoh query on key expressions starting with `my-site/`.
Now you can browse your site on http://localhost:8080/my-site.
.
.
For more advanced use cases you can also:
- Have the files of your web sites stored on different hosts. Running a zenoh
router with a File System Storage on
each host allow to make all the files available under the `my-site/` zenoh
key.
- Duplicate the files of your web sites on several hosts to provide fault
tolerance.
- Start several zenoh routers with the Web Service plugin on different hosts
(not necessarly the same than the
hosts running the File System storages). Each host will serve your web site.
- Use other backends than the File System to store your resources and make
them available through zenoh.
(List of available backends
[here](http://zenoh.io/docs/manual/backends-list/)).
- Deploy a zenoh application that will implement `eval` function for a
resource, replying to requests with a
dynamic content (see the `z_eval` example in
[Rust](https://github.com/eclipse-zenoh/zenoh/blob/main/zenoh/examples/zenoh/z_eval.rs)
or
[Python](https://github.com/eclipse-zenoh/zenoh-python/blob/main/examples/zenoh/z_eval.py)).
.
-------------------------------
## **Configuration**
.
In its configuration part, the plugin supports those settings:
- **`http_port`** - int or string - required:
either a port number as an integer or a string, either a string with format
`":"`
.
-------------------------------
## **Troubleshooting**
.
### *Address already in use*
If in `zenohd` logs you see such error log at startup:
```
[2021-04-12T14:20:51Z ERROR zenoh_plugin_webserver] Unable to start http server
for REST : Os { code: 48, kind: AddrInUse, message: "Address already in use" }
```
It means another process is already using this port number that the webserver
plugin would like to use.
In such case, you have 2 solutions:
- stop the other process using this port
- make the webserver plugin to another port changing its `listener` option.
.
### *Permission denied*
If in `zenohd` logs you see such error log at startup:
```
[2021-04-12T13:55:10Z ERROR zenoh_plugin_webserver] Unable to start http server
for REST : Os { code: 13, kind: PermissionDenied, message: "Permission denied"
```
It probably means your OS (this usually happens on Linux) forbids the usage of
the configured port for non-root user (actually it usually restricts all ports
between 0 and 1024).
In such case, you have 2 solutions:
- run zenohd with root privileges (via `sudo`)
- use another changing he webserver plugin's `listener` option.
.
-------------------------------
## **How to build it**
.
> :warning: **WARNING** :warning: : Zenoh and its ecosystem are under active
development. When you build from git, make sure you also build from git any
other Zenoh repository you plan to use (e.g. binding, plugin, backend, etc.).
It may happen that some changes in git are not compatible with the most recent
packaged Zenoh release (e.g. deb, docker, pip). We put particular effort in
mantaining compatibility between the various git repositories in the Zenoh
project.
.
> :warning: **WARNING** :warning: : As Rust doesn't have a stable ABI, the
plugins should be
built with the exact same Rust version than `zenohd`, and using for `zenoh`
dependency the same version (or commit number) than 'zenohd'.
Otherwise, incompatibilities in memory mapping of shared types between `zenohd`
and the library can lead to a `"SIGSEV"` crash.
.
At first, install [Cargo and
Rust](https://doc.rust-lang.org/cargo/getting-started/installation.html). If
you already have the Rust toolchain installed, make sure it is up-to-date with:
.
```bash
$ rustup update
```
.
To know the Rust version you're `zenohd` has been built with, use the
`--version` option.
Example:
```bash
$ zenohd --version
The zenoh router v0.6.0-beta.1 built with rustc 1.64.0 (a55dd71d5 2022-09-19)
```
Here, `zenohd` has been built with the rustc version `1.64.0`.
Install and use this toolchain with the following command:
.
```bash
$ rustup default 1.64.0
```
.
And `zenohd` version corresponds to an un-released commit with id `1f20c86`.
Update the `zenoh` dependency in Cargo.lock with this command:
```bash
$ cargo update -p zenoh --precise 1f20c86
```
.
Then build the backend with:
```bash
$ cargo build --release -p zenoh-plugin-webserver
```
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh-plugin-webserver
Vcs-Git: https://github.com/eclipse-zenoh/zenoh-plugin-webserver
Package: zenoh-plugin-webserver
Version: 1.0.0~rc.1-1
Architecture: armhf
Maintainer: zenoh-dev@eclipse.org
Installed-Size: 10059
Depends: zenohd (=1.0.0~rc.1-1)
Filename: 1.0.0-rc.1/zenoh-plugin-webserver_1.0.0~rc.1-1_armhf.deb
Size: 2133140
MD5sum: a2ba8ac249678d290e783ab02efb26a9
SHA1: 9d490b7f8652b5d7ed17a7a4f7d5a50143e8041c
SHA256: 31dbad083f1e7be8ddaca44cf605d65ba636fdf13fee7c52591fd789b9a014cc
Section: net
Priority: optional
Homepage: http://zenoh.io
Description: Plugin for Zenoh implementing an HTTP server that maps URLs to zenoh key
expressions
.
[](https://github.com/eclipse-zenoh/zenoh-plugin-webserver/actions?query=workflow%3A%22CI%22)
[](https://github.com/eclipse-zenoh/roadmap/discussions)
[](https://discord.gg/2GJ958VuHs)
[](https://choosealicense.com/licenses/epl-2.0/)
[](https://opensource.org/licenses/Apache-2.0)
.
# Eclipse Zenoh
The Eclipse Zenoh: Zero Overhead Pub/sub, Store/Query and Compute.
.
Zenoh (pronounce _/zeno/_) unifies data in motion, data at rest and
computations. It carefully blends traditional pub/sub with geo-distributed
storages, queries and computations, while retaining a level of time and space
efficiency that is well beyond any of the mainstream stacks.
.
Check the website [zenoh.io](http://zenoh.io) and the
[roadmap](https://github.com/eclipse-zenoh/roadmap) for more detailed
information.
.
-------------------------------
# Web Server plugin
.
The Web Server plugin implements an HTTP server mapping URLs to zenoh keys.
This plugin can be used to set-up a Web server where the resources are
retrieved from geo-distributed
zenoh storages, each leveraging various backends (file system, database,
memory...).
.
**Library name** `zenoh_plugin_webserver`
.
:point_right: **Download stable versions:**
https://download.eclipse.org/zenoh/zenoh-plugin-webserver/
.
:point_right: **Build "main" branch:** see [below](#How-to-build-it)
.
-------------------------------
## :warning: Documentation for previous 0.5 versions:
The following documentation related to the version currently in development in
"main" branch: 0.6.x.
.
For previous versions see the README and code of the corresponding tagged
version:
-
[0.5.0-beta.9](https://github.com/eclipse-zenoh/zenoh-plugin-webserver/tree/0.5.0-beta.9#readme)
-
[0.5.0-beta.8](https://github.com/eclipse-zenoh/zenoh-plugin-webserver/tree/0.5.0-beta.8#readme)
.
-------------------------------
## **Examples of usage**
.
Assuming you have a static website, you can:
- expose the files as zenoh key/values using the [File System
backend](https://github.com/eclipse-zenoh/zenoh-backend-filesystem)
- set-up this Web Server plugin that will allow HTTP clients to browse the
files.
.
Here are the steps:
1. Make sure the libraries for the File System backend and the Web Server
plugin are available for the zenoh router:
either installing their packages (depending your platform), either
downloading the library files corresponding
to your platform in your `~/.zenoh/lib` directory.
2. Copy the website files into a `~/.zenoh/zbackend_fs/my-site` directory (or
make it a symbolic link to the path of your website)
3. Create a `zenoh.json5` configuration file containing:
```json5
{
plugins: {
webserver: {
http_port: 8080,
},
storage_manager: {
volumes: {
fs: {}
},
storages: {
demo: {
key_expr: "my-site/**",
strip_prefix: "my-site",
volume: {
id: "fs",
dir: "my-site",
read_only: true
}
}
}
}
}
}
```
4. Start the zenoh router (`zenohd`). It will automatically load the Web
Server plugin and make it available on port 8080. It will also create a storage
replying to any zenoh query on key expressions starting with `my-site/`.
Now you can browse your site on http://localhost:8080/my-site.
.
.
For more advanced use cases you can also:
- Have the files of your web sites stored on different hosts. Running a zenoh
router with a File System Storage on
each host allow to make all the files available under the `my-site/` zenoh
key.
- Duplicate the files of your web sites on several hosts to provide fault
tolerance.
- Start several zenoh routers with the Web Service plugin on different hosts
(not necessarly the same than the
hosts running the File System storages). Each host will serve your web site.
- Use other backends than the File System to store your resources and make
them available through zenoh.
(List of available backends
[here](http://zenoh.io/docs/manual/backends-list/)).
- Deploy a zenoh application that will implement `eval` function for a
resource, replying to requests with a
dynamic content (see the `z_eval` example in
[Rust](https://github.com/eclipse-zenoh/zenoh/blob/main/zenoh/examples/zenoh/z_eval.rs)
or
[Python](https://github.com/eclipse-zenoh/zenoh-python/blob/main/examples/zenoh/z_eval.py)).
.
-------------------------------
## **Configuration**
.
In its configuration part, the plugin supports those settings:
- **`http_port`** - int or string - required:
either a port number as an integer or a string, either a string with format
`":"`
.
-------------------------------
## **Troubleshooting**
.
### *Address already in use*
If in `zenohd` logs you see such error log at startup:
```
[2021-04-12T14:20:51Z ERROR zenoh_plugin_webserver] Unable to start http server
for REST : Os { code: 48, kind: AddrInUse, message: "Address already in use" }
```
It means another process is already using this port number that the webserver
plugin would like to use.
In such case, you have 2 solutions:
- stop the other process using this port
- make the webserver plugin to another port changing its `listener` option.
.
### *Permission denied*
If in `zenohd` logs you see such error log at startup:
```
[2021-04-12T13:55:10Z ERROR zenoh_plugin_webserver] Unable to start http server
for REST : Os { code: 13, kind: PermissionDenied, message: "Permission denied"
```
It probably means your OS (this usually happens on Linux) forbids the usage of
the configured port for non-root user (actually it usually restricts all ports
between 0 and 1024).
In such case, you have 2 solutions:
- run zenohd with root privileges (via `sudo`)
- use another changing he webserver plugin's `listener` option.
.
-------------------------------
## **How to build it**
.
> :warning: **WARNING** :warning: : Zenoh and its ecosystem are under active
development. When you build from git, make sure you also build from git any
other Zenoh repository you plan to use (e.g. binding, plugin, backend, etc.).
It may happen that some changes in git are not compatible with the most recent
packaged Zenoh release (e.g. deb, docker, pip). We put particular effort in
mantaining compatibility between the various git repositories in the Zenoh
project.
.
> :warning: **WARNING** :warning: : As Rust doesn't have a stable ABI, the
plugins should be
built with the exact same Rust version than `zenohd`, and using for `zenoh`
dependency the same version (or commit number) than 'zenohd'.
Otherwise, incompatibilities in memory mapping of shared types between `zenohd`
and the library can lead to a `"SIGSEV"` crash.
.
At first, install [Cargo and
Rust](https://doc.rust-lang.org/cargo/getting-started/installation.html). If
you already have the Rust toolchain installed, make sure it is up-to-date with:
.
```bash
$ rustup update
```
.
To know the Rust version you're `zenohd` has been built with, use the
`--version` option.
Example:
```bash
$ zenohd --version
The zenoh router v0.6.0-beta.1 built with rustc 1.64.0 (a55dd71d5 2022-09-19)
```
Here, `zenohd` has been built with the rustc version `1.64.0`.
Install and use this toolchain with the following command:
.
```bash
$ rustup default 1.64.0
```
.
And `zenohd` version corresponds to an un-released commit with id `1f20c86`.
Update the `zenoh` dependency in Cargo.lock with this command:
```bash
$ cargo update -p zenoh --precise 1f20c86
```
.
Then build the backend with:
```bash
$ cargo build --release -p zenoh-plugin-webserver
```
Vcs-Browser: https://github.com/eclipse-zenoh/zenoh-plugin-webserver
Vcs-Git: https://github.com/eclipse-zenoh/zenoh-plugin-webserver