Document the production runtime profile behind evaluation and commercial deployments.

Deployment

Deployment explains how to run the Go site in a production profile without moving TLS termination into the app itself. It covers the container or VM runtime, the persistent SQLite volume used for lead and analytics data, the health-check endpoint, cache expectations at the edge, and the backup/restore path for production operations.

Coverage

What this section explains

  • Container or VM deployment profile with baked templates and static assets
  • Persistent SQLite volume for lead submissions and analytics events
  • TLS termination, cache headers, and probes handled by the reverse proxy or hosting edge
  • Backup, restore, and rollback checkpoints for production releases

Expected outputs

What teams should be able to leave with

  • Production deployment checklist
  • SQLite backup and restore runbook
  • Rollback and verification steps for operators

Primary audience

Who should start here

  • Platform teams planning hosted environments
  • Operations teams handling production recovery
  • Enterprise buyers evaluating data and recovery boundaries

Related docs

Continue with adjacent developer topics.

Product Overview

Platform architecture, capability map, and commercial packaging guidance for Realtek Connect+ evaluations.

View section

Development

Environment setup, team responsibilities, and implementation tracks for device, cloud, mobile, and operations teams.

View section

APIs

REST, MQTT over TLS, webhook, and service contract documentation entry points for external systems.

View section

SDKs

Mobile SDK, firmware SDK, reusable client components, and reference samples for branded product delivery.

View section

Firmware

Provisioning, identity, telemetry, OTA agent, and diagnostics expectations for device firmware teams.

View section

CLI

Command-line entry points for local testing, release preparation, fleet actions, and support diagnostics.

View section

Release Notes

Versioned change logs, upgrade notes, compatibility statements, and rollout communication patterns.

View section