Docker Environment for 1C-Bitrix: PHP 8.1, Xdebug, MySQL, Redis

Problem: FTP and Production — a Dangerous Combination

Developing Bitrix directly on a production server via FTP is like performing surgery on a moving vehicle. A single typo in a file takes the site down. Over the years, we've seen dozens of projects where such cost-cutting led to a full day of downtime. A local environment with proper configuration is the only way to develop offline, use a debugger, and test database schema changes without fear. We offer turnkey Docker environment setup: PHP 8.1, MySQL 8, Redis, Xdebug, Mailpit, and production data import. This solves the environment consistency problem and reduces new developer onboarding from two days to two hours — direct budget savings. We'll evaluate your project in one day.

Why a Local Environment Is Critical

Without a local environment, you cannot debug AJAX requests, test integrations with 1C and payment gateways, or test changes in information blocks. Any code error immediately becomes visible to users. Docker solves this: it isolates the environment and gives full control over PHP versions, extensions, and services. You get the exact same configuration as production, without the risk.

Docker vs Other Tools: Which to Choose?

Docker wins on all key parameters: portability, consistency, and speed. For teams of 2–10 developers, it's the standard.

How to Configure Xdebug for Bitrix

Xdebug is a must-have for debugging. In the php container, enable:

[xdebug]
xdebug.mode = debug
xdebug.start_with_request = yes
xdebug.client_host = host.docker.internal
xdebug.client_port = 9003
xdebug.idekey = PHPSTORM

[opcache]
opcache.enable = 0  ; Disable OPcache for development

In PHPStorm: Settings → PHP → Servers → add a server named bitrix-local, host localhost, configure path mappings: /path/to/project/www → /var/www/html. Then you can set breakpoints and inspect the stack.

Why Docker Is the Best Choice for Bitrix Environment

Docker addresses the main pain point: consistency. One docker-compose.yml gives every developer an identical environment. No more "it works on my machine" situations. We reduced new developer onboarding from two days to two hours thanks to Docker. And with image caching, it's even faster. Docker provides isolation and reproducibility of the environment (Wikipedia)

Turnkey Setup Process

1. Analysis — determine PHP and MySQL versions, needed extensions (gd, imagick, soap, etc.)
2. Docker Build — write Dockerfile and docker-compose.yml
3. Configuration — Xdebug, php.ini, nginx, database
4. Data Import — copy DB via mysqldump, files via rsync, configure dbconn.php to use environment variables
5. Documentation — README with commands for start, deployment, common issues
6. Team Training — show how to use Xdebug, Mailpit, Git

What's Included in the Work

• Docker environment (PHP 8.1, MySQL 8, Redis, Mailpit)
• Xdebug configuration with path mappings
• Import of a database copy and files from production
• Configuration of dbconn.php and .env
• Documentation (README, commands for start, cache clearing)
• One hour of post-delivery support

Timeline and Cost

Basic environment setup takes 1 to 3 days. Cost is calculated individually — it depends on complexity (custom modules, non-standard extensions). We guarantee quality: over 10 years of experience with Bitrix, certified specialists, 50+ successful projects. Request a consultation — we'll find the optimal solution for your budget.

Typical Mistakes When Setting Up Yourself

• Forgetting to disable OPcache — code doesn't update, hours lost.
• Confusing paths in Xdebug — debugger fails.
• Not syncing upload/ and DB — local environment doesn't match production.
• Committing dbconn.php with passwords — risk of leakage.

Conclusion

A configured Docker environment for Bitrix is speed, consistency, and safety. The stack used: Docker Compose, PHP 8.1, MySQL 8, Redis, Mailpit, Xdebug. More about Docker — Wikipedia. Official Bitrix documentation — dev.1c-bitrix.ru.

Comparing PHP Versions for Bitrix

We recommend PHP 8.1 or 8.2 for maximum performance and compatibility.

What Professional 1C-Bitrix Installation Includes

We start by checking innodb_buffer_pool_size. The default MySQL value (128 MB) is a death sentence for an online store with a catalog of 10,000+ items. We set 70–80% of available RAM on a dedicated server, 50% on VPS. This single setting speeds up the site by 2–3 times compared to the default. We'll assess your project in one day — get a consultation. Contact us to order turnkey installation with performance guarantee.

How to Choose Hosting and Edition for 1C-Bitrix Installation?

BitrixVM is a virtual machine with a pre-installed stack: nginx + Apache, PHP-FPM, MySQL/MariaDB, Sphinx, Push server. For VPS — the best start. Everything is already configured for Bitrix, including OPcache, log rotation, and firewall. Management via web panel on port 8890. Bitrix documentation recommends starting with BitrixVM for predictable performance.

VPS/VDS is the sweet spot. Minimum configuration for a medium online store: 2 vCPU, 4 GB RAM, SSD. Optimal: 4 vCPU, 8 GB RAM. OS: Ubuntu 22.04 or Debian 12. If not BitrixVM, we configure the stack manually for the task. Virtual hosting — only for business cards and landing pages. Requirements: PHP 8.0+, MySQL 5.7+ / MariaDB 10.0+, 512 MB RAM, .htaccess. 1C-Bitrix hosting partners guarantee compatibility. Dedicated server — for highload. Typical architecture: web server separate, database separate, Redis/Memcached separate. For Enterprise edition — web cluster with load balancer. Cloud (Yandex Cloud, VK Cloud, Selectel) — when load spikes: sales, seasonal peaks. Autoscaling via Managed Kubernetes or simple VM vertical scaling.

Choosing the edition is equally important. A common mistake: choosing "Small Business" for a store that grows to B2B with wholesale prices and three warehouses in six months. Upgrading to "Business" — pay the difference, data is not lost, but it's better to plan ahead. Our specialists select the edition for current tasks and with room for growth. For example, the "Business" license (about 35,000 RUB) pays off through multi-warehouse and 1C exchange, while the wrong choice can lead to a loss of up to 30,000 RUB monthly on excess resources.

What Server Settings Are Critical for 1C-Bitrix?

Web Server and PHP

nginx as reverse proxy + Apache (mod_php) or nginx + PHP-FPM directly. The second option saves memory — Apache is not needed. But some Bitrix modules use .htaccess, so for compatibility we sometimes keep Apache. nginx configuration: fastcgi_read_timeout 300 — for long operations (1C import), client_max_body_size 1024m — large file uploads. Block access to .settings.php, .settings_extra.php, bitrix/.settings.php — they contain database passwords. Rewrite rules from urlrewrite.php — Bitrix generates them, but with nginx + PHP-FPM they need to be duplicated. PHP 8.0–8.2 with extensions: mbstring, curl, gd, xml, json, opcache, redis/memcached. Key php.ini settings: opcache.memory_consumption=256, opcache.max_accelerated_files=20000, max_execution_time=300, memory_limit=512M, upload_max_filesize=100M, post_max_size=128M.

Database and Caching

MySQL/MariaDB. Key my.cnf parameters: innodb_buffer_pool_size — 70–80% RAM, innodb_log_file_size=256M, tmp_table_size=256M, max_heap_table_size=256M, thread_pool_size — number of CPU cores. Encoding utf8mb4 mandatory, otherwise emoji and special characters break. Redis is preferable to Memcached for Bitrix — supports persistent connections and is more reliable. In production, Redis handles concurrent writes three times faster than Memcached under typical load. Configure in .settings_extra.php:

'cache' => ['value' => ['type' => ['class_name' => '\\Bitrix\\Main\\Data\\CacheEngineRedis']]]
'session' => ['value' => ['mode' => 'default', 'handlers' => ['general' => ['type' => 'redis']]]]

sudo apt install redis-server
sudo systemctl enable redis

SSL, Email, and Cron

SSL — Let's Encrypt via certbot in 90% of cases. Redirect HTTP → HTTPS (301), HSTS, TLS 1.2/1.3, OCSP Stapling. In Bitrix, switch to HTTPS in the main module settings. Email: abandon mail() — connect SMTP (Yandex.Mail for domain, Mail.ru for Business). Be sure to configure SPF, DKIM, DMARC. Without SPF, emails go to spam. Test deliverability via mail-tester.com — score 9+/10. Cron: Bitrix agents switch to system cron — * * * * * /usr/bin/php /var/www/bitrix/modules/main/tools/cron_events.php. Schedule 1C exchange (15–60 min), search reindex, backups (mysqldump + rsync, rotation 7+4), temporary file cleanup.

Security and Administration

File system: owner www-data, directories 755, files 644, upload 775. nginx blocks access to configuration files. Enable Bitrix Proactive Protection — WAF, activity control (block after 5 failed attempts), kernel integrity check. For admin panel: two-factor authentication via Google Authenticator or OTP, restrict access by IP via nginx for paranoid.

How Long Does 1C-Bitrix Installation and Configuration Take?

Post-Installation Checklist

1. Performance Monitor (/bitrix/admin/perfmon_panel.php) — aim for 30+ points. Below 20 means serious configuration issues.
2. System Check — automatic check of all parameters. Red items must be fixed, yellow — case by case.
3. Security Scanner — check for typical vulnerabilities.
4. PageSpeed Insights — TTFB < 200ms on VPS, LCP < 2.5s.
5. Test 1C exchange — if integration is planned, verify CommerceML exchange before launch.

Additionally, check software versions, caching settings, cron operation, SSL certificate, SPF/DKIM/DMARC, access rights, delete default users and pages. For projects with 54-FZ, ensure fiscalization is configured via OFD provider.

Deliverables

• Fully configured server for 1C-Bitrix with MySQL, PHP, nginx optimization.
• Installed and activated license of the required edition.
• SSL certificate, email settings, cron and backups.
• Documentation: all configuration parameters, access credentials, cron tasks.
• Content manager training: how to log into admin panel, add products, upload images.
• Post-installation support for 30 days — consultations on settings.

Why Trust Professionals with Installation?

Incorrect installation means lost time and money. We've seen projects where a store on "Start" couldn't handle 50 visitors because innodb_buffer_pool_size wasn't configured. After migrating to VPS with correct configuration, the site "flew". Incorrect configuration can cost 30,000 RUB monthly due to excessive resource consumption. You get a ready-made architecture that scales. Order turnkey 1C-Bitrix installation — get a reliable platform for business growth. Contact us for a free consultation: we'll calculate the cost and time for your project. Over 7 years of experience, 120+ Bitrix projects implemented, including highload stores with million-item catalogs. Get in touch — we'll help configure Bitrix for your project.