anfimovdm · Oct 25, 2026 · Oct 25, 2026
diff --git a/.gitignore b/.gitignore
@@ -133,20 +133,9 @@ override.tf.json
 .terraformrc
 terraform.rc
 
-# Ignore sensitive files from deployment
-deployment/hosts
-deployment/ansible
-deployment/hosts.*
-deployment/files/*.pem
-deployment/files/*.crt
-deployment/files/*/*.pem
-deployment/files/*/*.crt
-deployment/*vars*.yml
-deployment/*vars*.yaml
+# Deployment moved to the albs-deploy repository, ignore leftover local
+# inventories, vars and certificates
+deployment/
 
 # Ignore venvs of all kind
 *venv
-
-# Ignore Ansible dependencies
-deployment/roles/geerlingguy.redis
-deployment/roles/geerlingguy.docker
diff --git a/README.md b/README.md
@@ -140,6 +140,12 @@ Few preparations needed before you start:
 To start the system, run the following command: `docker-compose up -d`. This command will pull RabbitMQ image, build docker images for Celery and Scheduler containers and start the containers themselves. To rebuild images after your local changes, just run `docker-compose up -d --build`.
 
 
+Deploying to servers
+--
+
+Ansible roles and playbooks for deploying RabbitMQ, the scheduler (with Flower) and Celery workers live in the [albs-deploy](https://github.com/AlmaLinux/albs-deploy) repository, see the ALTS section of its README.
+
+
 Running in virtualenv
 --
 You can start the application inside virtualenv. Create virtualenv:

diff --git a/deployment/ansible.cfg b/deployment/ansible.cfg
diff --git a/deployment/celery_playbook.yml b/deployment/celery_playbook.yml
diff --git a/deployment/files/celery/ca_certificate.pem b/deployment/files/celery/ca_certificate.pem
diff --git a/deployment/files/celery/client_certificate.pem b/deployment/files/celery/client_certificate.pem
diff --git a/deployment/files/celery/client_key.pem b/deployment/files/celery/client_key.pem