Environments

Keep every environment isolated

Each LCE environment has its own base URL, credentials, data and external integrations. Keep these values outside application code and promote the same build through your delivery pipeline.

Recommended environment model

Your project may use fewer or additional stages. The names below describe a common delivery model; confirm the environments enabled for your Lidia deployment.

Development

Build and integrate

Developer testing, disposable data and sandbox provider connections.

Test or QA

Verify behavior

Automated tests, integration validation and controlled test datasets.

Staging or UAT

Validate releases

Production-like configuration and business acceptance before release.

Production

Serve live traffic

Live data, production providers, restricted access and full monitoring.

Configure the API base URL

The LCE API definitions represent the server as https://{yourLidiaUrl}. Replace it with the hostname assigned to the target environment.

# .env.development
LCE_BASE_URL=https://api.dev.example.com
LCE_TOKEN=<development-jwt>
LCE_TENANT_ID=1

# .env.production
LCE_BASE_URL=https://api.example.com
LCE_TOKEN=<production-jwt>
LCE_TENANT_ID=1

What must remain separate

Configuration	Non-production	Production
Credentials	Environment-specific identities with test permissions.	Restricted identities using least-privilege permissions.
Commerce data	Synthetic, anonymized or approved test data.	Live customer and operational data.
Providers	Payment, logistics, ERP and notification sandboxes.	Live provider accounts and production callback URLs.
Observability	Developer diagnostics and test alerts.	Operational dashboards, audit trails and actionable alerts.
Network access	Controlled access for engineering and test systems.	Approved origins, allowlists, private routes and TLS configuration.

Deployment model

LCE supports cloud and on-premises deployments. Supported cloud platforms include Amazon Web Services, Microsoft Azure and Huawei Cloud. Depending on the project architecture, LCE can run on Kubernetes or virtual machines.

The deployment model does not change how clients authenticate or construct API paths; it determines who manages infrastructure, networking, scaling and operations.

Environment readiness checklist

HTTPS base URL resolves from the calling system
JWT credential flow is confirmed
Required roles and permissions are assigned
Tenant and application context are known
CORS or gateway rules are configured where required
Provider sandbox or production accounts are connected
Callback and webhook URLs target the correct environment
Timeouts, logs, metrics and alerts are configured