ScottiBYTE MultiView Server v1.3.0

This release updates the server client-management experience for the expanded ScottiBYTE MultiView ecosystem, including Android TV, Fire TV, phones, and tablets.

Added

• Renamed the client management page from TV Clients to Remote Clients.
• Added clearer remote-client sections:
  • Pending Authorization
  • Approved - Waiting for First Connection
  • Authorized Clients
• Added delete support for stale pending authorization requests.
• Added delete support for approved clients that never complete first connection.
• Added client display-name rename support for authorized clients.
• Updated the server UI version label to v1.3.0.

Improved

• Updated server wording to reflect TV, mobile, tablet, and remote clients.
• Removed unnecessary internal client IDs from the main client-management view.
• Improved Remote Clients page readability and documentation value.

Compatibility

• Existing /api/tv/... client API endpoints remain unchanged.
• Existing Android TV / Fire TV clients remain compatible.
• Existing Android Mobile clients remain compatible.
• Existing authorized clients continue to work.

Docker Pull

docker pull scottibyte/multiview-server:1.3.0

v1.2.0 - Container-managed stream publishers

ScottiBYTE MultiView Server v1.2.0

Container-managed stream publishers

This release improves the Docker deployment model for ScottiBYTE MultiView Server. Enabled camera streams are now started and managed automatically by the MultiView Server container using FFmpeg.

A clean Docker deployment can now publish camera streams to MediaMTX without requiring any separate stream-publisher setup outside the server container.

Added

• Container-managed FFmpeg publishers for enabled cameras
• Automatic publisher startup when the server container starts
• Automatic publisher restart when camera settings are saved
• Automatic publisher cleanup when cameras are deleted
• FFmpeg installed directly inside the MultiView Server Docker image
• Self-contained Docker image packaging for clean pulls and fresh installs
• Docker build cleanup to exclude local backup files and development artifacts

Fixed

• Clean Docker installs now include the required application files under /app
• Camera stream publishing now starts automatically from the server container
• Local server.js.before-* backup files are excluded from Docker images
• Release image no longer depends on local source files being mounted into the container
• Updated the displayed app version and GitHub release link to v1.2.0

Verified

• Clean scratch-server Docker deployment tested successfully
• Container starts the FFmpeg publisher automatically
• MediaMTX receives the published camera stream
• HLS returns a working playlist
• Dev server verified with multiple enabled camera publishers

Docker image

docker pull scottibyte/multiview-server:1.2.0

Latest tag:

docker pull scottibyte/multiview-server:latest

Basic verification

After starting the stack, confirm the server container is running:

docker ps --format "table {{.Names}}\t{{.Status}}\t{{.Image}}"

Confirm FFmpeg publishers are running inside the server container:

docker exec -it multiview-server sh -lc 'pgrep -a ffmpeg'

Confirm MediaMTX sees ready streams:

curl -s http://127.0.0.1:9997/v3/paths/list

ScottiBYTE MultiView Server v1.1.0

ScottiBYTE MultiView Server v1.1.0

Initial public GitHub release of ScottiBYTE MultiView Server.

Highlights

• Self-hosted web UI for configuring RTSP cameras
• Camera grouping for TV client organization
• MediaMTX-backed HLS stream publishing
• First-run administrator setup
• Secure Android TV / Fire TV client pairing
• Read-only TV client camera catalog API
• Dashboard, camera list, groups, stream engine, and TV client management pages
• Automatic thumbnail refresh support
• Light and dark mode
• Docker-friendly deployment

Security Model

Camera credentials remain on the self-hosted server. Android TV / Fire TV clients do not receive raw RTSP URLs, camera usernames, or camera passwords. TV clients must be paired and approved from the server web UI.

Documentation

The README includes setup instructions, screenshots, architecture overview, camera configuration workflow, TV client pairing, reverse proxy notes, and community support information.