VLStream Cloud v1.2.1

VLStream Cloud v1.2.1

This release is built from origin/main and integrates with the independently
published APaaS WVP Server v1.0.1.

Highlights

• Unified VLStream, GB28181, ONVIF, RTSP, ISUP, and Dahua device access through the WVP device center.
• Added tenant-aware token exchange, shadow identities, and event-delivery isolation.
• Added device classification across protocol sources and refreshed the device-management experience.
• Added firmware package management, deployment jobs, OTA status tracking, and rootfs-only delivery support.
• Improved MQTT device state handling, media upload validation, GPU training scheduling, and timeout recovery.
• Refined navigation, page layout, icons, tables, and algorithm-training workflows.

Deployment

• VLStream images are ghcr.io/oortcloudgroup/vlstream-backend:1.2.1 and ghcr.io/oortcloudgroup/vlstream-frontend:1.2.1.
• WVP is deployed separately from ghcr.io/oortcloudgroup/apaas-wvp-server:1.0.1 and must be started before VLStream.
• When both products run on the same host, set WVP_HTTP_PORT=9080 in the WVP .env, then keep the VLStream WVP upstream at http://host.docker.internal:9080.
• Use the same ZLMediaKit secret in both deployments so VLStream can reuse the media server started by WVP.
• Extract the archive, copy .env.example to .env, replace every example password and secret, and run docker compose up -d.

Database

• New installations import the sanitized VLStream initialization SQL.
• Existing installations receive immutable Flyway migrations for firmware management, GPU scheduler metadata, tenant shadow identities, and event-report delivery.
• Back up the database before upgrading and never edit a Flyway migration that has already run.

Full Changelog: https://github.com/OortCloudGroup/VLStream-Cloud/commits/v1.2.1

VLStream Cloud v1.2.0

VLStream Cloud v1.2.0

This release is built from the current origin/main baseline and extends the
one-command deployment with the WVP protocol backend and ZLMediaKit.

Highlights

• Added independent WVP and ZLMediaKit containers for GB28181, ONVIF, and RTSP workflows.
• Added same-origin frontend routing through /bus/wvp-server/; browser requests no longer depend on a separately configured WVP address.
• Added VLStream token federation between the WVP backend and the primary backend.
• Added an independent ry-wvp database in the shared MySQL instance and Redis database index 10.
• Added Flyway-managed WVP database initialization and future upgrades.
• Removed device records, media-node records, local network addresses, and third-party keys from the public WVP baseline.
• Kept Linux ISUP and Dahua native SDK listeners disabled by default until their vendor runtimes are installed and verified.

Deployment

• Default images are ghcr.io/oortcloudgroup/vlstream-backend:1.2.0, ghcr.io/oortcloudgroup/vlstream-frontend:1.2.0, and ghcr.io/oortcloudgroup/vlstream-wvp-backend:1.2.0.
• Extract the release archive, copy .env.example to .env, update every change-me value, and run docker compose up -d.
• For device access from another computer, set SIP_PUBLIC_IP and ZLMEDIAKIT_PUBLIC_HOST to the Docker host's reachable address and open the documented SIP/media ports.

Database

• New VLStream installations import sql/init/10-oortcloud-workflowforms-vls.sql.
• Compose creates the separate WVP database; the WVP container then initializes and upgrades it with Flyway.
• Existing installations retain their named volumes and receive immutable Flyway migrations when the corresponding backend starts.
• Back up both databases before upgrading. Do not manually execute Flyway migration copies from sql/upgrade.

Full Changelog: https://github.com/OortCloudGroup/VLStream-Cloud/commits/v1.2.0

VLStream Cloud v1.1.3

VLStream Cloud v1.1.3

This release packages the current origin/main after v1.1.2 with the latest device, video, model-dispatch, training, and frontend navigation updates.

Highlights

• Added VLS-Protocol 2.2 model dispatch, signed model transfer, device media handling, and durable model conversion status tracking.
• Added model-training scheduler and container configuration support, together with algorithm-library and city-management seed migrations.
• Added V2 event-group management and unified active-safety navigation flows.
• Updated video playback and camera preview paths, including WebRTC snapshot fallback behavior.
• Grouped frontend routes into edge intelligence and cloud intelligence navigation sections.
• Added the core business and technical architecture reference with hardware lifecycle, video, messaging, storage, and dependency diagrams.

Database

• New and existing installations use sql/init/10-oortcloud-workflowforms-vls.sql for the baseline schema.
• Flyway applies V1_1_3_001 through V1_1_3_005 automatically when the v1.1.3 backend starts.
• Back up existing databases before upgrading. Do not manually execute Flyway migration copies from sql/upgrade.

Deployment

• Default images are ghcr.io/oortcloudgroup/vlstream-backend:1.1.3 and ghcr.io/oortcloudgroup/vlstream-frontend:1.1.3.
• Extract the archive and run docker compose up -d for bundled MySQL, Redis, MinIO, WebRTC-streamer, backend, and frontend services.
• Use docker compose -f compose.external.yaml up -d to reuse externally managed MySQL and Redis services.

Full Changelog: https://github.com/OortCloudGroup/VLStream-Cloud/commits/v1.1.3

VLStream Cloud v1.1.2

VLStream Cloud v1.1.2

This patch release starts from origin/main at 00fc9ee and improves standalone algorithm-library initialization and API compatibility.

Fixes

• Removed all legacy database views from the public MySQL initialization script. These views referenced private apaas_* databases and are not used by the standalone application.
• Proxied active-safety task APIs to the packaged backend instead of serving them as missing frontend assets.
• Routed workflow and work-order requests to the current backend service and removed the legacy development-service endpoint.
• Prevented duplicate /bus/vls-server prefixes in job-server requests generated by the production frontend.
• Stabilized the algorithm-training table width so production builds no longer expand the layout continuously.
• Kept the release source based on origin/main; only the documented standalone and deployment fixes are added.
• Added checksummed release-build copies of the SmartJavaAI 1.1.0 artifacts used by main, avoiding incompatible binaries currently resolving under the same public coordinates.
• Supplied standalone-only settings through Compose so startup does not require private XXL Job or unified messaging configuration.
• Normalized Windows-tolerated import casing only inside the ephemeral Linux frontend build context.
• Added release validation that rejects external database references and conflicting backend logging bindings.
• Normalized algorithm repository status values to the numeric 1/0 representation returned by the backend while retaining compatibility with legacy enabled/disabled payloads.
• Added an idempotent basic algorithm repository migration with seven generic presets and no private model paths, development URLs, or test records.

Deployment

• New installations use the supplied schema at sql/init/10-oortcloud-workflowforms-vls.sql, including the basic algorithm repository and seven generic presets.
• Run docker compose up -d after extracting the release archive.
• Existing installations should deploy v1.1.2 images, recreate the backend and frontend containers, and apply sql/upgrade/24-base-algorithm-presets.sql after backing up the database.

Full Changelog: https://github.com/OortCloudGroup/VLStream-Cloud/commits/v1.1.2

VLStream Cloud v1.1.1

VLStream Cloud v1.1.1

This patch release starts from origin/main and includes the standalone deployment fixes found during clean Docker Compose validation.

Fixes

• Removed all legacy database views from the public MySQL initialization script. These views referenced private apaas_* databases and are not used by the standalone application.
• Proxied active-safety task APIs to the packaged backend instead of serving them as missing frontend assets.
• Routed workflow and work-order requests to the current backend service and removed the legacy development-service endpoint.
• Prevented duplicate /bus/vls-server prefixes in job-server requests generated by the production frontend.
• Stabilized the algorithm-training table width so production builds no longer expand the layout continuously.
• Kept the release source based on origin/main; only the documented standalone and deployment fixes are added.
• Added checksummed release-build copies of the SmartJavaAI 1.1.0 artifacts used by main, avoiding incompatible binaries currently resolving under the same public coordinates.
• Supplied standalone-only settings through Compose so startup does not require private XXL Job or unified messaging configuration.
• Normalized Windows-tolerated import casing only inside the ephemeral Linux frontend build context.
• Added release validation that rejects external database references and conflicting backend logging bindings.

Deployment

• New installations still use the supplied schema at sql/init/10-oortcloud-workflowforms-vls.sql; only unused legacy views are omitted.
• Run docker compose up -d after extracting the release archive.
• Existing v1.1.0 installations should deploy v1.1.1 images and recreate the backend and frontend containers. Back up the database before applying any upgrade SQL.

Full Changelog: https://github.com/OortCloudGroup/VLStream-Cloud/commits/v1.1.1

VLStream Cloud v1.1.0

VLStream Cloud v1.1.0

This release extends the one-click deployment introduced in v1.0.0 with WebRTC live streaming and adds Hi3519DV500 model export and deployment support.

Highlights

• Added a WebRTC-streamer v0.8.16 container, same-origin reverse proxying, health checks, and UDP media port configuration.
• Added backend WebRTC runtime configuration and a health-status gateway; the frontend playback entry now reuses the runtime service address.
• Added support for exporting models to the Hi3519DV500 SVP ACL OM format and deploying them to target hardware.
• Added OM format support to the model download interface and introduced the om_model_output_path database migration.
• Switched the frontend to local authentication and improved the workspace, video playback, search, table, and tab layouts.
• Added English and Chinese product screenshots and a Hi3519DV500 model deployment guide.
• Added a complete but sanitized MySQL initialization structure. On first startup, the backend safely restores the administrator account, menus, dictionaries, and required workflow data.

Deployment

• The default Compose bundle includes MySQL, Redis, MinIO, WebRTC-streamer, the backend, and the frontend. Start everything with docker compose up -d.
• New deployments use the oortcloud_workflowforms_vls database. The initialization SQL retains only the required Flowable version metadata and excludes development workflow instances, logs, devices, and recordings.
• For live playback from another computer, set WEBRTC_EXTERNAL_HOST and allow UDP ports 50000-50010 on the server.
• Before upgrading an existing database, create a backup and review the scripts under sql/upgrade in the release package.

Full Changelog: https://github.com/OortCloudGroup/VLStream-Cloud/commits/v1.1.0

VLStream Cloud v1.0.0

VLStream Cloud v1.0.0

This is the first official release of VLStream Cloud, including the frontend, backend, and a complete Docker Compose setup for local deployment.

Deployment Features
Public frontend and backend images are available on GHCR.

The default Docker Compose configuration includes MySQL, Redis, and MinIO, allowing the entire system to be started with:

docker compose up -d
An alternative deployment configuration is provided for connecting to external MySQL and Redis services.
Release assets include a clean initialization SQL script, historical data, and database upgrade scripts, published unchanged according to the 4C plan.

Before deploying to a production environment, change all default passwords and read the README.zh-CN.md file included in the release package.

Full Changelog: https://github.com/OortCloudGroup/VLStream-Cloud/commits/v1.0.0