Downcity
Configuration

Configuration Checklist

Production/readiness checks before rollout

Configuration Checklist

Use this checklist before release:

  1. Model binding
  • Verify ship.json.model.primary exists in city console model list.
  1. Routing and network
  • Verify start.host/start.port match runtime daemon.
  • Ensure no stale DC_SERVER_* env values.
  1. Channels and services
  • Enable only required channels/services.
  • Run one send/receive test per enabled channel.
  1. Permissions and security
  • Confirm permissions.exec_command.deny covers high-risk commands.
  • Ensure DC_MODEL_DB_KEY is injected securely.
  1. Observability
  • Confirm log paths are writable and traceable.
  • Check city console status and city agent status are healthy.

Model Configuration (Console + Agent)

Responsibility boundary between model pool and project binding

Security and Permissions Overview

User-facing security model for isolation, permissions, and secret protection

Table of Contents

Configuration ChecklistRelated docs