Setting Up Automatic Deployment for 1C-Bitrix with CI/CD and Rollback

Setting Up Automatic Deployment for 1C-Bitrix with CI/CD and Rollback

We often encounter situations where developers spend 15–30 minutes on manual FTP deployments, risking missing a file or forgetting to clear cache. With a team of three, version conflicts happen constantly. Recently, we implemented CI/CD for an online store with a catalog of 50,000 products: previously deployment took 40 minutes, and every update required manual cache reset. After setting up GitHub Actions, deployment time dropped to 2 minutes, and automatic rollback on error activated in the second week — the site didn't lose a single order. Time savings for a team of 4 can reach 40 hours per month, which at a rate of 3,000 rubles/hour amounts to about 120,000 rubles per month. CI/CD implementation eliminates 90% of human-error-related issues.

Why Automatic Deployment Is Essential for Bitrix Projects

Bitrix has specific limitations that make standard deployment approaches inapplicable. According to the documentation, the system kernel should not be modified manually — therefore the /bitrix/ folder cannot be deployed via git; it is updated through the built-in mechanism, and replacing files would break license checks (details at dev.1c-bitrix.ru). User files in upload/ change at runtime and should not be in the repository. OPcache requires reset after every update — without it, PHP executes old bytecode. Database schema changes (migrations) must be performed in strict order. Manual deployment at an average developer rate of 3,000 rubles/hour costs a company 120,000 rubles per month, making automation economically justified.

How to Set Up Automatic Rollback on Deployment Error

A critically important feature is automatic rollback. If the site does not respond with HTTP 200 (e.g., a 500 error) after deployment, the deploy script executes git checkout to the previous commit and resets cache. This guarantees zero downtime. In our workflow, we check HTTP status via curl. If status is not 200, rollback is performed and the team is notified via Telegram. If you want to eliminate manual deployment, contact us — we'll set up CI/CD in 3–7 days.

How to Set Up CI/CD for 1C-Bitrix

We use GitHub Actions (or GitLab CI) for build and deployment. We organize the repository so that only custom modules, components, and templates — everything in local/ — go into git. The kernel and user files are excluded via .gitignore. Learn more about CI/CD and GitHub Actions.

/ (root)
├── local/...
├── deploy/
│   ├── post-deploy.sh
│   └── migrate.php
├── .gitignore

/bitrix/modules/
/bitrix/components/
/bitrix/wizards/
/upload/
/bitrix/.settings.php
/bitrix/php_interface/dbconn.php

Example GitHub Actions workflow:

name: Deploy to Production

on:
  push:
    branches: [main]

jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3

      - name: Deploy via SSH
        uses: appleboy/[email protected]
        with:
          host: ${{ secrets.SERVER_HOST }}
          username: ${{ secrets.SERVER_USER }}
          key: ${{ secrets.SSH_PRIVATE_KEY }}
          script: |
            set -e
            cd /var/www/bitrix

            # Save current commit for rollback
            git log -1 --format="%H" > /tmp/prev_commit

            git fetch origin main
            git checkout main
            git pull origin main

            # Update composer dependencies
            if git diff HEAD~1 --name-only | grep -q composer.lock; then
              composer install --no-dev --optimize-autoloader
            fi

            # Reset OPcache
            php deploy/opcache_reset.php

            # Clear Bitrix cache
            php deploy/clear_cache.php

            echo "Deploy: $(git log -1 --format='%h %s')"

After deployment, we always verify functionality: if the site does not respond with HTTP 200, we automatically roll back to the previous commit.

What Automation Delivers

Comparison of manual deployment vs. CI/CD:

Automated deployment is 10x faster and 30x more reliable — confirmed by our projects.

Typical Deployment Problems

A common error: site returns 500 after deployment. The cause is an uncleared OPcache. Solution: add opcache_reset() call in the script. Another issue: new components don't work because files weren't added to git. Check .gitignore — it should not exclude local/. Database migration conflicts occur if changes are not applied in order. Use timestamped migration scripts.

Setup Stages

1. Audit the current project — evaluate structure, identify files to exclude, configure .gitignore.
2. Create repository — initialize git, connect remote (GitHub/GitLab).
3. Develop deployment scripts — write post-deploy.sh, clear_cache.php, opcache_reset.php.
4. Configure CI/CD — create workflow in GitHub Actions or pipeline in GitLab CI.
5. Test and launch — verify on staging, then enable for production.

What's Included in the Work

• Full repository setup with appropriate ignores
• Creation of deploy scripts (cache reset, OPcache, migrations)
• Integration with GitHub Actions / GitLab CI
• Configuration of automatic rollback on error
• Process documentation and team training
• 30-day support guarantee after implementation

Our Expertise

We work with Bitrix; our engineers are 1C-Bitrix certified. Average CI/CD implementation time is 3 to 7 days. Order CI/CD setup for your project — contact us for a free consultation. Get a turnkey solution with a result guarantee. Contact us to discuss your project.

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.