1. Home
  2. Docs
  3. Getting started
  4. First deployment checklist
Getting started

First deployment checklist

A practical checklist for moving from a fresh environment to a usable OneTALA installation.

Developer v2026.10 Updated 4 Nov 2026

Before deployment

  • Create DNS records and decide the public, workspace, Flow, and UAT domains.
  • Provision PostgreSQL/PostGIS, Redis, persistent storage, and SMTP/SMS services required by enabled modules.
  • Generate application, JWT, database, Redis, blind-index, and internal service secrets securely.
  • Decide whether operational files stay on persistent local storage or S3-compatible object storage.
  • Configure backups before importing production data.

Deploy the application

composer install --no-dev --optimize-autoloader
npm ci --no-audit --no-fund
npm run build
php artisan migrate --force
php artisan modules:sync
php artisan modules:check
php artisan optimize:clear
php artisan optimize
php artisan horizon:terminate

In container deployments, run these inside the application container or a dedicated migration task.

Validate before users arrive

Test login, permission scope, file uploads, queues, scheduler, email, TALA Flow form publish/submit/export, Campaign mobile sync, dashboards, and a database restore procedure. Do not consider a deployment complete only because the home page returns HTTP 200.

Was this page helpful?

Still stuck?

Open a ticket and reference this page — we will pick it up from there.

Open a ticket