🛠️ DevOps Tips 🛠️ If your GitHub workflows or jobs are failing due to jobs concurrently accessing and/or modifying shared resources, You can control execution at the workflow or job levels using the concurrency.
Jobs/Workflows in the same are prohibited from running at the same time, and you can cancel any jobs/workflow if you trigger another one.
Groups let you define compartments in which you don't want concurrent workflows running. They can be organized however you like. I find that using them in separate environments is a great practice.
Cancel-in-progress: specifies if the old running job/workflow needs to shut down.
Read more in docs: https://docs.github.com/en/actions/how-tos/write-workflows/choose-when-workflows-run/control-workflow-concurrency
I build reliable backends, DevOps systems & data pipelines.
New to Contra
I build reliable backends, DevOps systems & data pipelines.
Inception is a containerized web infrastructure project built with Docker and Docker Compose. I configured Nginx with TLS, WordPress with PHP-FPM, and MariaDB as isolated services, including persistent storage, secure networking, environment configuration, and automated service orchestration. It demonstrates my DevOps, Linux, containerization, and infrastructure engineering skills.
Webserv is a custom HTTP/1.1 server built from scratch in C++98. I implemented non-blocking network communication, request parsing, routing, static file serving, uploads, CGI execution, and configurable error handling. The project demonstrates my skills in backend engineering, networking, systems programming, and protocol design.