DockerCP product updates

Keep fresh installations and upgrades aligned with the expanded DockerCP template catalog.

• Add Botpress, Drone, Hermes Agent, OpenClaw, Bolt.Diy, and Metaflow to the canonical installer template catalog.
• Update the existing Drone Runner template with its approved runtime configuration and Docker socket requirement.
• Carry the same template definitions into the upgrade path so existing 3.1.9 installations and fresh 3.1.10 installations receive the same catalog data.
• Preserve the existing template runtime capabilities used for command overrides, host access, Docker socket mounts, persistent storage, and health checks.
• Rebuild the 3.1.10 customer release artifacts from the updated canonical source.

Bring the application source, installation schemas, migrations and downloadable packages into a consistent DockerCP 3.1.9 release.

• Correct the full-dump retry path for the license entitlement table.
• Fix Glance capability JSON while preserving its starter YAML configuration.
• Preserve template catalog seeds when generating the customer database schema.
• Align shared columns, indexes and migration checksums across full and customer databases.
• Validate imports, repeat imports and migration reruns with native MariaDB 10.11.
• Expand regression checks for PHP queries, package integrity, scheduled jobs and matching release archives.

Synchronize installation paths and improve checks around existing deployments.

• Keep the root and publicly served installer scripts identical.
• Verify downloaded release checksums before database setup.
• Preserve the existing environment and runtime storage during application replacement.
• Use the PHP worker account for required permissions and background jobs without changing existing workload data ownership.

Make downloadable release archives consistent and easier to verify.

• Build one versioned customer archive and copy the same bytes to the latest download.
• Regenerate SHA256 files, per-file manifests and latest-release metadata.
• Normalize archive paths, ordering, timestamps and permissions.
• Check customer packages for missing dependencies and forbidden private or runtime files.

Improve validation of service snapshot content and supported restore operations.

• Verify snapshot payload checksums and reject missing backup data.
• Validate the target service before applying restored configuration.
• Restore saved environment and runtime configuration for supported service snapshots.
• Reject unsupported persistent-data clone operations and incomplete backup types.

Make background collection and maintenance part of the installed customer package.

• Ship the monitoring collector and daily maintenance scripts with customer releases.
• Schedule both jobs with locks that prevent overlapping runs.
• Retain job errors in runtime logs and return failure exit codes when appropriate.
• Add resource-alert and certificate-issue notification sources to supported checks.

Align builder availability and deployment feedback with the local Docker runtime.

• Check the Docker daemon and Compose plugin before reporting builder availability.
• Reuse the same builder health checks in settings and API tests.
• Correct container inspection commands used by runtime checks.
• Report unavailable runtime integrations and deployment-state write failures explicitly.

Make settings screens reflect saved configuration and improve notification error handling.

• Load real notification, certificate and storage-provider records.
• Display empty states when no saved configuration exists.
• Remove invalid fallback rows from database parameter arrays.
• Retain notification delivery errors and allow failed channels to be retried.

Improve MariaDB compatibility and make schema upgrade failures easier to diagnose.

• Quote the databases table identifier consistently in runtime queries and migrations.
• Enforce the required domain and database uniqueness indexes.
• Report duplicate-data conflicts without silently discarding affected records.
• Correct database field references and SQL parameter mismatches in affected operations.

Improve configuration handling between the installer, runtime and settings pages.

• Use a shared environment parser with consistent quoted-value handling.
• Give process settings precedence over the project environment file.
• Preserve installation identity and encryption keys during existing-install updates.
• Report unsuccessful settings writes instead of displaying an unsaved success state.

Improve how application templates describe the configuration required by their containers.

• Add template runtime drivers, capability metadata and health-check definitions.
• Support template bootstrap files and application-specific persistent storage settings.
• Refine deployment configuration for supported catalog applications.
• Preserve existing template IDs and service relationships during catalog updates.

Separate the customer control panel distribution from vendor-only website and billing components.

• Add signed entitlement verification and a local entitlement cache.
• Integrate license status and plan information into the settings interface.
• Package the self-hosted panel with its own installation schema and migration files.
• Exclude vendor credentials, private signing material and live account data from customer releases.

Expand product guidance and simplify administration of public content and platform settings.

• Organize documentation, blog articles and product release notes.
• Add content metadata and SEO fields to administrative editors.
• Improve settings navigation and account management screens.
• Preserve POST action handling alongside clean public and panel URLs.

Configure notification destinations and select the operational events they receive.

• Add saved notification channels with event filtering.
• Support email, webhook and supported messaging-service adapters.
• Emit notifications for deployment success and failure.
• Expose channel testing and delivery status in notification settings.

Connect account plans with billing information and enforceable resource allowances.

• Introduce plan-aware pricing and account onboarding flows.
• Display subscription and billing information in the vendor application.
• Apply plan limits to projects, services and managed databases.
• Keep community limits available for self-hosted customer installations.

Strengthen authentication and access checks across the control panel.

• Add login-attempt tracking and rate-limit checks.
• Improve CSRF validation across authenticated forms and API actions.
• Apply user and project permission checks to protected operations.
• Add reCAPTCHA verification for configured authentication flows.

Extend application operations with snapshots for supported services and configurable backup storage.

• Capture service configuration together with supported persistent-data payloads.
• Add service snapshot listing, download and restore workflows.
• Introduce storage-provider configuration for supported backup destinations.
• Record snapshot status and operational errors for recovery troubleshooting.

Manage supported database services alongside the applications that use them.

• Add database records associated with projects and services.
• Store database connection settings and encrypted credentials.
• Expose supported database operations through the panel.
• Apply project ownership and plan limits to database management.

Bring host and container information together with deployment logs and recorded panel actions.

• Display host resource information and local container statistics.
• Add monitoring views for managed services.
• Expose deployment output and service logs in the dashboard.
• Improve activity history for project, service and administrative operations.

Connect custom domains to services and manage their routing configuration through the panel.

• Associate domains with deployed services and select primary domains.
• Generate Traefik routing labels for supported service deployments.
• Add domain DNS checks and certificate status inspection.
• Expose routing and certificate information in domain management screens.

Connect service configuration to local Docker Compose deployments and routine container operations.

• Generate Compose configuration from service and template settings.
• Support deployment and redeployment through the local Docker Engine.
• Add start, stop and removal actions for managed services.
• Record deployment output and operational activity for troubleshooting.

Find application templates and review their deployment requirements before creating a service.

• Expanded the categorized application template catalog.
• Added template descriptions, recommended resources and documentation links.
• Defined template environment variables, exposed ports and persistent storage requirements.
• Improved category filtering and template detail pages.

Organize applications into projects and manage their service configuration from the dashboard.

• Added project creation, editing and deletion workflows.
• Introduced service configuration within individual projects.
• Added project and service ownership checks.
• Improved dashboard navigation between projects, services and activity history.

The foundation of a self-hosted control panel for managing Docker applications from a central web interface.

• Established the core account, project and service database structure.
• Introduced the authenticated control panel and primary navigation.
• Added application configuration, session handling and shared platform settings.
• Created the public product website and initial documentation structure.