automation

When a project moves beyond local development and starts using CI/CD, a fundamental question arises: how to securely pass configuration parameters into build and deployment pipelines. This concerns not only database passwords, but also container registry tokens, SSH keys, JWT signing keys, message queue connection strings, and any other parameters that must not be stored in plain text.

Sensitive data ending up in a Git repository is not just bad practice. The commit history is kept forever. Even if a secret is removed in a later commit, it has already become part of the history and can be retrieved via git log, git show or when cloning a fork. In a corporate environment this becomes a real risk during audits, team expansion, or if repository access is leaked.

When working on real projects (CDN change, migration, refactor) you often need to bulk-replace one URL with another.

At first glance the task seems trivial: sed -i 's|old|new|g' **/* — and done.

In reality that approach is Russian roulette.

A careless replacement leads to:

• 💀 Corruption of binary files (images, pdf, archives);
• 📉 Garbage in git history (binaries marked as changed);
• 🚫 Inability to cleanly roll back if a backup wasn’t made.

In this note we’ll cover a production-grade algorithm: change only text, don’t touch binaries, make a targeted backup.

Jitsi Meet works out of the box very well for video conferencing. The Jitsi Meet + Jibri bundle allows you to record meetings — and many installations stop there.

But as soon as Jitsi is used not occasionally, but as part of a working process, questions arise very quickly:

• Where should recordings be stored centrally?
• How can links be automatically published for the team?
• How can we get rid of heavy MP4 files and move to streaming playback?
• How can recordings be served over HTTPS without exposing the directory structure?
• How can all of this be done automatically, without manual administrator involvement?

Below is a full production pipeline with code: from Jibri finalizing a recording to publishing in Notion and asynchronous MP4→HLS transcoding with delivery via Caddy.

n8n is a powerful open-source workflow automation tool that allows building complex workflows without deep programming. One of the key scaling mechanisms in n8n is queue mode, where the main instance delegates task execution to separate processes called workers. Workers allow distributing load, enabling parallel workflow execution and improving system performance.

In the n8n community and practical guides, two types of workers are often distinguished: light workers and heavy workers. Although the official documentation doesn’t use these terms directly, they reflect differences in task types and configuration. Light workers are aimed at fast, frequent operations, while heavy workers handle resource-intensive tasks. In this article we’ll examine their differences, how they work, and why they are necessary for effective scaling.

Introduction

Business process automation has become a standard: whether it’s integrating CRM with messengers, data processing, or DevOps tasks. In this article, we’ll look at what automation tools exist, how they differ, and how to choose the right solution for your needs.

SaaS Platforms

Zapier

Zapier is one of the oldest and most popular automation services (since 2011). Its strength is its huge ecosystem: more than 5000 integrations, including CRMs, messengers, marketing, and financial tools.

Introduction

WP-CLI is the official command-line tool for WordPress, allowing you to manage your sites without logging into the admin panel. With WP-CLI, you can install plugins, update WordPress core, manage users, handle database tasks, and even run advanced automation workflows.

In this guide, we’ll explore what WP-CLI is, how to install it, and provide practical examples of its most useful commands.

What is WP-CLI?

WP-CLI (WordPress Command Line Interface) is a PHP-based tool that enables direct interaction with WordPress through the terminal. It covers almost all admin tasks and sometimes goes beyond the WordPress dashboard:

n8n + Xano: A Powerful No-Code Backend for Scalable Applications

In the final article of our series on n8n integrations with backend services, we’re taking a closer look at Xano — a no-code/low-code platform for building scalable APIs and databases without writing server-side code.

If you need a flexible, fast-to-deploy backend with support for scalability and automation, the Xano + n8n combination is an excellent choice.

What Is Xano?

Xano is a cloud platform for visually building backends and APIs. Under the hood, it runs on PostgreSQL, while on the surface it offers a powerful API Builder for creating logic, DB operations, and integrations — all without writing code.

n8n + Appwrite: An Open-Source Firebase Alternative for Self-Hosting

We’ve already explored Supabase and Firebase — now it’s time to look at Appwrite, a powerful and fully open-source BaaS platform designed for self-hosting and complete data control.

If you want to build a backend on your own infrastructure, Appwrite can be the perfect partner in combination with n8n.

What Is Appwrite?

Appwrite is a full-featured Backend as a Service (BaaS) platform with open-source code. It provides REST APIs for most features a modern application needs:

n8n + Firebase: NoSQL, Realtime Database, and Cloud Functions for Dynamic Apps

After reviewing Supabase and its PostgreSQL-based architecture, let’s turn to another powerful BaaS platform — Firebase by Google. Firebase takes a completely different approach: NoSQL, real-time data sync, and deep integration with the Google Cloud ecosystem.

If your app needs real-time updates, schema flexibility, and strong mobile support, the Firebase + n8n combo might become your key automation tool.

n8n + Supabase: PostgreSQL, Authentication, and API All in One

We continue our series on n8n’s integration with backend services. Today’s focus is Supabase — a popular open-source Firebase alternative built on PostgreSQL. Supabase delivers everything a modern backend needs — DB, authentication, API, realtime — and integrates seamlessly with n8n.

What Is Supabase?

Supabase is a BaaS (Backend-as-a-Service) that brands itself as an “open-source Firebase alternative,” powered by PostgreSQL. It offers: