Development Environment

A development environment lets you test templates, API requests, and client-site changes before publishing them to the production domain.

What to Prepare

Component	Purpose
Local web server	Run the client site and check routes
PHP and Composer	Work with the CMS client, dependencies, and templates
Node.js	Build frontend assets when the theme uses npm packages
Git	Track changes and prepare releases
Panel access	Get project, server, and API settings

Local Domain

Use a separate local domain, for example project.loc. It should point to the same site root that will be used on hosting.

Do not use the production domain for experiments with templates, payments, and authentication. This keeps test keys, temporary settings, and debug logs separate.

Project Configuration

Check local connection settings:

• project domain;
• project ID;
• selected platform;
• default server;
• interface language;
• /graphql availability.

If the local site calls the public API, send only documented headers and variables. The common request format is described in Request Format.

Debugging

Enable detailed errors only locally. Keep technical fields in logs: documentId, HTTP status, request id, and error category.

Do not log passwords, PIN codes, 2FA codes, tokens, payment details, or private keys.

Pre-Publish Check

Before moving changes, check:

• the home page and main routes;
• registration, login, and logout;
• server selection;
• player cabinet opening;
• payment flow in test mode;
• responsive layout on mobile width;
• no browser console errors.