cCoder Ltd
Guest (Login)

First Time Setup

View the baseline assets

Create the first administrator and let Core establish the fixed tenant, first application and packaged platform baseline.

When this page appears

Core shows the setup page when the configured environment has not yet been initialised. The Core and SSO connection strings select the databases before the application starts; startup migrations prepare their schemas. The form does not choose a database, tenant or domain.

The cCoder.Core first-time setup form showing the FirstAdminUserDetails fields and Submit details action

Fill in the first administrator

  • DisplayName is the administrator name shown by the platform.
  • Email identifies the administrator. The part before the @ is used for the initial sign-in request.
  • Password supplies the initial account password.
  • ConfirmPassword must match before setup can begin.

Select Submit(details); once. Keep the page open while the progress dialog reports each stage.

Defaults and assumptions

  • The tenant ID is fixed to default.
  • The tenant name is fixed to cCoder Default.
  • The first application is named cCoder Default and belongs to tenant default.
  • The application domain is inferred from the current request host.
  • The default theme is Default, the default culture is initially empty, and application configuration starts as {}.
  • The configured Core and SSO databases are expected to be reachable and suitable for startup migration.

What setup does

  1. Creates the fixed tenant and the first administrator through /Api/Setup.
  2. Signs in the administrator through /Api/Account/Login.
  3. Creates the first application for the detected domain.
  4. Downloads the common cache and application baseline packages.
  5. Imports both packages through /Api/Core/Package/Import.
  6. Redirects to the platform root when every stage completes.

The browser coordinates these steps rather than submitting one database transaction. If a stage fails, read the progress log and inspect what completed before retrying; do not assume an automatic rollback.

Where the baseline comes from

The setup page downloads two versioned JSON packages from the cCoder.Assets repository under Packages/First Time Setup.

  • common-cache.json supplies shared cache definitions used across the platform.
  • app-baseline.json supplies the starter application pages, layouts, templates, scripts and resources.

Treat those files as the source-controlled baseline. Changes to first-time content belong in cCoder.Assets so new environments import the same reviewed package definitions.

After setup

Core opens the new platform at its root URL. Continue configuration from the administration UI; the first-time form is only the bootstrap boundary and is not the place to maintain tenant, domain or application settings afterward.