Update README.md

This commit is contained in:
Santiago Lo Coco 2025-01-01 16:15:49 +01:00
parent 706e616830
commit 82f1f66646
1 changed files with 2 additions and 2 deletions

View File

@ -9,7 +9,7 @@ Instead of hardcoding endpoints and needing to redeploy the app every time you w
- **Automatic service discovery**: Registers as an `_http._tcp.` service using Zeroconf, making it easily discoverable on the network.
- **Lightweight REST API**: Minimal yet robust API for managing WebRTC endpoints.
- **Responsive and bloat-free**: Built with vanilla JS and HTML for fast, adaptable performance on any device.
- **SQLite database**: Uses SQLite by default, easily extendable to other databases by adjusting the endpoint.
- **SQLite database**: Uses SQLite by default, easily extendable to other databases by adjusting the database endpoint.
## Prerequisites
@ -54,7 +54,7 @@ Note that by default, the API initializes with predefined endpoints unless `DEFA
- `/api/endpoints/1: {"url": "http://$SERVICE_IP:8100/mystream/"}`
- `/api/endpoints/2: {"url": "http://$SERVICE_IP:8200/mystream/"}`
Here, we use the service IP, which matches the IP address for the API. This way, we don't rely on DNS resolution, which can sometimes have issues. The main task is to access the API endpoint, which can be done either through the service IP or with Zeroconf. You can also use a custom mDNS client that follows RFC 6762 and RFC 6763, like the one implemented in [WebView](https://github.com/se23m504/WebView).
Here, we use the service IP, which matches the IP address for the API. This way, we don't rely on DNS resolution, which can sometimes have issues. The main task is to access the API endpoint, which can be done either through the service IP or with Zeroconf. You can also use a custom mDNS client that follows RFC 6762 and RFC 6763, like the one implemented in [WebViewStream](https://git.slc.ar/slococo-uni/webviewstream).
### cURL examples