Building a 1C-Bitrix website using Terraform

To create an infrastructure for your 1C-Bitrix website using Terraform:

1. Prepare your cloud.
2. Create an infrastructure.
3. Configure a server for 1C-Bitrix.
4. Configure 1C-Bitrix.

If you no longer need the resources you created, delete them.

Prepare your cloudPrepare your cloud

Sign up for Yandex Cloud and create a billing account:

1. Go to the management console and log in to Yandex Cloud or create an account if you do not have one yet.
2. On the Yandex Cloud Billing page, make sure you have a billing account linked and it has the ACTIVE or TRIAL_ACTIVE status. If you do not have a billing account, create one.

If you have an active billing account, you can go to the cloud page to create or select a folder for your infrastructure to operate in.

Learn more about clouds and folders.

Required paid resourcesRequired paid resources

1C-Bitrix server and database support cost includes:

• Fee for Yandex Compute Cloud disks and a continuously running VM (see Compute Cloud pricing).
• Fee for using a dynamic or static public IP address (see Yandex Virtual Private Cloud pricing).
• Fee for using a managed DB (see Managed Service for MySQL® pricing).

This tutorial uses the trial version of 1C-Bitrix with a 30-day trial period. You can check the cost of the product software versions on the 1C-Bitrix official website.

Create an infrastructureCreate an infrastructure

Terraform allows you to quickly create a cloud infrastructure in Yandex Cloud and manage it using configuration files. Configuration files store the infrastructure description in the HashiCorp Configuration Language (HCL). Terraform and its providers are distributed under the Business Source License.

For more information about the provider resources, see the documentation on the Terraform website or the mirror.

If you change the configuration files, Terraform automatically detects which part of your configuration is already deployed, and what should be added or removed.

To create an infrastructure using Terraform:

1. Install Terraform, get the authentication credentials, and specify the source for installing the Yandex Cloud provider (see Configure a provider, step 1).

2. Prepare files with the infrastructure description:

   Ready-made configuration

   Manually

   1. Clone the repository with configuration files.

      git clone https://github.com/yandex-cloud-examples/yc-bitrix-website.git
      

   2. Go to the directory with the repository. Make sure it contains the following files:

      • bitrix-website.tf: New infrastructure configuration.
      • bitrix-website.auto.tfvars: User data file.

   1. Create a directory for configuration files.
   2. In the directory, create:

      1. bitrix-website.tf configuration file:

         bitrix-website.tf

         variable "folder_id" {
           type = string
         }
         
         variable "vm_user" {
           type = string
         }
         
         variable "ssh_key_path" {
           type = string
         }
         
         variable "mysql_user" {
           type = string
         }
         
         variable "mysql_password" {
           type = string
           sensitive = true
         }
         
         terraform {
           required_providers {
             yandex = {
               source  = "yandex-cloud/yandex"
               version = ">= 0.47.0"
             }
           }
         }
         
         provider "yandex" {
           zone = var.folder_id
         }
         
         resource "yandex_vpc_network" "network-1" {
           name = "network1"
         }
         
         resource "yandex_vpc_subnet" "subnet-1" {
           name           = "subnet1"
           zone           = "ru-central1-a"
           network_id     = yandex_vpc_network.network-1.id
           v4_cidr_blocks = ["192.168.1.0/24"]
         }
         
         resource "yandex_vpc_subnet" "subnet-2" {
           name           = "subnet2"
           zone           = "ru-central1-b"
           network_id     = yandex_vpc_network.network-1.id
           v4_cidr_blocks = ["192.168.2.0/24"]
         }
         
         resource "yandex_vpc_subnet" "subnet-3" {
           name           = "subnet3"
           zone           = "ru-central1-d"
           network_id     = yandex_vpc_network.network-1.id
           v4_cidr_blocks = ["192.168.3.0/24"]
         }
         
         resource "yandex_vpc_security_group" "sg-vm" {
           name        = "bitrix-sg-vm"
           description = "Description for security group"
           network_id  = yandex_vpc_network.network-1.id
         
           egress {
             protocol       = "ANY"
             description    = "ANY"
             v4_cidr_blocks = ["0.0.0.0/0"]
             from_port      = 0
             to_port        = 65535
           }
         
           ingress {
             protocol       = "TCP"
             description    = "EXT-HTTP"
             v4_cidr_blocks = ["0.0.0.0/0"]
             port           = 80
           }
         
           ingress {
             protocol       = "TCP"
             description    = "EXT-SSH"
             v4_cidr_blocks = ["0.0.0.0/0"]
             port           = 22
           }
         
           ingress {
             protocol       = "TCP"
             description    = "EXT-HTTPS"
             v4_cidr_blocks = ["0.0.0.0/0"]
             port           = 443
           }
         }
         
         resource "yandex_vpc_security_group" "sg-mysql" {
           name        = "bitrix-sg"
           description = "Security group for mysql"
           network_id  = yandex_vpc_network.network-1.id
         
           egress {
             protocol       = "ANY"
             description    = "any"
             v4_cidr_blocks = ["0.0.0.0/0"]
             from_port      = 0
             to_port        = 65535
           }
         
           ingress {
             protocol       = "TCP"
             description    = "ext-msql"
             v4_cidr_blocks = ["0.0.0.0/0"]
             port           = 3306
           }
         }
         
         data "yandex_compute_image" "ubuntu-image" {
           family = "ubuntu-2204-lts"
         }
         
         resource "yandex_compute_disk" "boot-disk" {
           name     = "bootdisk"
           type     = "network-ssd"
           zone     = "ru-central1-a"
           size     = "24"
           image_id = data.yandex_compute_image.ubuntu-image.id
         }
         
         resource "yandex_compute_instance" "vm-bitrix" {
           name        = "bitrixwebsite"
           platform_id = "standard-v3"
           zone        = "ru-central1-a"
         
           resources {
             core_fraction = 20
             cores         = 2
             memory        = 4
           }
         
           boot_disk {
             disk_id = yandex_compute_disk.boot-disk.id
           }
         
           network_interface {
             subnet_id          = yandex_vpc_subnet.subnet-1.id
             security_group_ids = ["${yandex_vpc_security_group.sg-vm.id}"]
             nat                = true
           }
         
           metadata = {
              user-data = "#cloud-config\nusers:\n  - name: ${var.vm_user}\n    groups: sudo\n    shell: /bin/bash\n    sudo: 'ALL=(ALL) NOPASSWD:ALL'\n    ssh_authorized_keys:\n      - ${file("${var.ssh_key_path}")}"
           }
         }
         
         resource "yandex_mdb_mysql_cluster" "bitrix-cluster" {
           name               = "BitrixMySQL"
           environment        = "PRESTABLE"
           network_id         = yandex_vpc_network.network-1.id
           version            = "8.0"
           security_group_ids = ["${yandex_vpc_security_group.sg-mysql.id}"]
         
           resources {
             resource_preset_id = "s2.micro"
             disk_type_id       = "network-hdd"
             disk_size          = "10"
           }
         
           host {
             zone             = "ru-central1-a"
             subnet_id        = yandex_vpc_subnet.subnet-1.id
             assign_public_ip = false
           }
         
           host {
             zone             = "ru-central1-b"
             subnet_id        = yandex_vpc_subnet.subnet-2.id
             assign_public_ip = false
           }
         }
         
         resource "yandex_mdb_mysql_database" "bitrix-db" {
           cluster_id = yandex_mdb_mysql_cluster.bitrix-cluster.id
           name       = "db1"
         }
         
         resource "yandex_mdb_mysql_user" "bitrix-user" {
           cluster_id = yandex_mdb_mysql_cluster.bitrix-cluster.id
           name       = var.mysql_user
           password   = var.mysql_password
           permission {
             database_name = yandex_mdb_mysql_database.bitrix-db.name
             roles         = ["ALL"]
           }
         }
         

      2. bitrix-website.auto.tfvars user data file:

         bitrix-website.auto.tfvars

         folder_id      = "<folder_ID>"
         vm_user        = "<VM_username>"
         ssh_key_path   = "<path_to_public_SSH_key_file>"
         mysql_user     = "<DB_username>"
         mysql_password = "<DB_user_password>"
         

   For more information about the parameters of resources used in Terraform, see the provider documentation:

   • Network: yandex_vpc_network
   • Subnets: yandex_vpc_subnet
   • Security groups: yandex_vpc_security_group
   • Image: [yandex_compute_image](https://terraform-provider.yandexcloud.net/Resources/compute_image }})
   • Disk: [yandex_compute_disk](https://terraform-provider.yandexcloud.net/Resources/compute_disk }})
   • VM instance: yandex_compute_instance
   • MySQL cluster: yandex_mdb_mysql_cluster
   • Database: yandex_mdb_mysql_database
   • Database user: yandex_mdb_mysql_user

3. In the bitrix-website.auto.tfvars file, set the user-defined parameters:

   • folder_id: Folder ID.
   • vm_user: VM username.
   • ssh_key_path: Path to the file with a public SSH key to authenticate the user on the VM. For more information, see Creating an SSH key pair.
   • mysql_user: Username for connecting to the MySQL® DB. In this tutorial, specify user1.
   • mysql_password: User password to access the MySQL® DB. In this tutorial, specify p@s$woRd!.

4. Create resources:

   1. In the terminal, change to the folder where you edited the configuration file.

   2. Make sure the configuration file is correct using the command:

      terraform validate
      

      If the configuration is correct, the following message is returned:

      Success! The configuration is valid.
      

   3. Run the command:

      terraform plan
      

      The terminal will display a list of resources with parameters. No changes are made at this step. If the configuration contains errors, Terraform will point them out.

   4. Apply the configuration changes:

      terraform apply
      

   5. Confirm the changes: type yes in the terminal and press Enter.

Configure a server for 1C-BitrixConfigure a server for 1C-Bitrix

To configure a server for 1C-Bitrix:

1. Connect to the VM over SSH on behalf of the user specified when creating the VM, e.g., ubuntu:

   ssh ubuntu@<VM_public_IP_address>
   

   You can look up the VM's public IP address in the management console by checking the Public IPv4 address field under Network on the VM page.

2. Install the required software:

   sudo apt-get update
   sudo apt-get install -y apache2 libapache2-mod-php php-gd php-mbstring php-mysql
   

3. Go to the project's working directory and download the 1C-Bitrix: Site Management distribution:

   cd /var/www/html/
   sudo wget https://www.1c-bitrix.ru/download/business_encode.tar.gz
   

4. Unpack the downloaded archive and delete unnecessary files:

   sudo tar -zxf business_encode.tar.gz
   sudo rm -f index.html business_encode.tar.gz
   

5. Make the www-data user the owner of the project's working directory:

   sudo chown -R www-data:www-data /var/www/html
   

   Check the permissions and owners of the working folder:

   ls -l
   

   Result:

   total 40
   drwxrwxr-x 7 www-data www-data  4096 Jun  8  2023 bitrix
   -rwxrwxr-x 1 www-data www-data  1150 Nov 30  2020 favicon.ico
   -rwxrwxr-x 1 www-data www-data  1353 Jun  8  2023 index.php
   -rwxrwxr-x 1 www-data www-data   268 Apr 17  2023 install.config
   -rwxrwxr-x 1 www-data www-data 12821 Mar 18  2022 readme.html
   -rwxrwxr-x 1 www-data www-data   112 Mar 27  2013 readme.php
   drwxrwxr-x 2 www-data www-data  4096 Jun  8  2023 upload
   

6. For 1C to work correctly, configure the PHP settings. To do this, use the built-in nano editor and modify the following variables in the php.ini configuration file:

   sudo nano /etc/php/8.1/apache2/php.ini
   

   Previously	Now
   short_open_tag = Off	short_open_tag = On
   memory_limit = 128M	memory_limit = 256M
   ;date.timezone =	date.timezone = Europe/Moscow
   ;opcache.revalidate_freq =2	opcache.revalidate_freq =0
   ;session.save_path = "/var/lib/php/sessions"	session.save_path = "/var/lib/php/sessions"

   The php.ini file path depends on the PHP version installed. The example shows the path for version 8.1. For version 8.0, enter /etc/php/8.0/apache2/php.ini, for version8.2, enter /etc/php/8.2/apache2/php.ini, and so on.

   Tip

   To find the parameter you need in the nano editor, press Ctrl + W. Find the required parameter from the table above and save the changes using Ctrl + O. To exit the editor, press Ctrl + X.

7. Configure the Apache web server. To do this, edit the /etc/apache2/sites-enabled/000-default.conf configuration file.

   1. Open the file in the text editor:

      sudo nano /etc/apache2/sites-enabled/000-default.conf
      

   2. Add the following section after the DocumentRoot /var/www/html line and save the changes:

      <Directory /var/www/html>
        Options Indexes FollowSymLinks
        AllowOverride All
        Require all granted
      </Directory>
      

   3. Restart the web server to apply all the updated settings:

      sudo systemctl restart apache2
      

After you run these commands, the server side will be configured for 1C-Bitrix to work correctly.

Configure 1C-BitrixConfigure 1C-Bitrix

Install and configure 1C-Bitrix:

1. Open the 1C-Bitrix: Site Management web interface at http://<VM_public_IP_address>/. This should open a page prompting you to install 1C-Bitrix.

2. Click Next.

   

3. Read the license agreement and select I accept the license agreement. Then click Next.

   

4. Registration is optional, so you can uncheck the corresponding checkbox, but leave Install in UTF-8 encoding and click Next.

   

5. 1C-Bitrix will check if the server is configured correctly. View the parameters on this page and click Next.

   

6. Configure the database:

   1. In the Server field, enter the fully qualified domain name (FQDN) of the DB you created. To find out this name:
      1. In the management console, open the folder page in a new browser tab.
      2. In the list of services, select Managed Service for MySQL.
      3. In the window that opens, select the BitrixMySQL cluster you created earlier.
      4. Select the Hosts tab in the left-hand menu.
      5. In the Host FQDN field, hover over the host name (format: rc1c-cfazv1db********) and copy the database FQDN by clicking the icon that appears. The FQDN will be added to the host name, so the Server field should contain a name in rc1c-cfazv1db********.mdb.yandexcloud.net format.
   2. In the Username and Password fields, enter the data that you specified when creating the DB in Create a MySQL® DB cluster.
   3. In the Database name field, specify the name of the created DB (db1).
   4. Click Next.

   

7. Wait for the MySQL® DB to initialize.

   

8. Create an administrator account authorized to make changes to your system. Fill in all the fields and click Next.

   

9. Select the Information portal template and click Next.

   

10. Confirm the selection of the only layout template available and click Next.

    

11. Select a color and click Next.

    

12. Fill in all the fields according to your website requirements and click Install to start the installation and configuration of all the system components. Wait for its completion.

    

13. After a while, a notification page will open to inform you that the system is installed and configured. To start using the website, click Go to website.

    

14. You can now start working with the ready-to-use web interface in content editing mode.

    

15. To view the website home page as a user, exit your website administration mode. To do this, click Exit in the top-right corner of the page and go to http://<VM_public_IP_address>/.
    To return to edit mode, log in to the website using the administrator credentials you provided when configuring 1C-Bitrix.

    

How to delete the resources you createdHow to delete the resources you created

To stop paying for the resources you created:

1. Open the bitrix-website.tf configuration file and delete from it the description of the infrastructure you created.

2. Apply the changes:

   1. In the terminal, change to the folder where you edited the configuration file.

   2. Make sure the configuration file is correct using the command:

      terraform validate
      

      If the configuration is correct, the following message is returned:

      Success! The configuration is valid.
      

   3. Run the command:

      terraform plan
      

      The terminal will display a list of resources with parameters. No changes are made at this step. If the configuration contains errors, Terraform will point them out.

   4. Apply the configuration changes:

      terraform apply
      

   5. Confirm the changes: type yes in the terminal and press Enter.

See alsoSee also

• Building a 1C-Bitrix website using the management console.