[BACKEND] External phone camera management #4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is this PR about
In this PR we try to use the web interface to link local network devices cameras to feed the dataset.
How do we plan to do it
In the camera configuration dropdown, add a special camera option called "Phone".
This option must:
When a "Phone" camera is added:
🔍 Determine frontend base address:
localhostor127.0.0.1, detect the machine's local network IP address (e.g.,192.168.x.x).🔐 Enable HTTPS locally (required for camera access on phones):
https://<local_ip>:<port>over Wi-Fi🌐 Setup a WebRTC streaming endpoint on the backend:
📱 Generate a mobile streaming link with QR code:
[https://<local_ip>:<port>]/remote_cam/[webrtc_id]getUserMedia🖥️ Frontend UI behavior:
🔁 Stream routing from phone to frontend:
Implementation constraints:
mkcert,selfsigned,flask-tls)Optional:
Related PRs