Tag: devops
All the articles with the tag "devops".
-
Multiple Actions with a Single docker exec Call
Run multiple commands in one docker exec call using sh -c — pipe commands, chain with && or ;, and avoid repeated container roundtrips.
-
Executing Commands with Asterisks in Docker
Shell globbing breaks inside docker exec because of how args are parsed — here's how to pass wildcards and asterisks correctly.
-
Tmux for Streamlining Dev Workflow
tmux sessions, windows, and panes for developers — layouts, plugins, and the .tmux.conf that makes it feel like a proper IDE.
-
Ansible vs. Terraform: Cloud Infrastructure Management
Ansible configures servers; Terraform provisions infrastructure — learn when to use each, how they overlap, and why you probably need both.
-
WordPress, Docker, NGINX, and MySQL via Ansible
Automate a full WordPress stack deployment — Docker, nginx, and MySQL — using Ansible playbooks instead of clicking through wizards.
-
DevOps Tools: Ansible vs. Puppet vs. Salt vs. Chef
Ansible, Puppet, Salt, and Chef all do configuration management — but they're very different. Pick the right one before you commit.
-
Optimizing Ansible for Faster Playbook Execution
Speed up Ansible playbooks with pipelining, forks, fact caching, and async tasks — stop watching the spinning wheel on every play.
-
Uptime Monitoring with Uptime Kuma
Uptime Kuma monitors your services and sends alerts when they go down — beautiful self-hosted alternative to UptimeRobot.
-
Automating Docker via Ansible
Automate Docker container deployment with shell scripts, cron, and Ansible — stop SSHing in and restarting things by hand.
-
Observability and Monitoring for Containers
Logs, metrics, and traces for Docker containers — Prometheus, Loki, Grafana, and OpenTelemetry to know what's happening inside your stack.
-
Docker vs Podman: Key Differences
Docker needs a daemon; Podman doesn't. Compare architecture, rootless support, Compose compatibility, and which one belongs in your workflow.
-
Understanding PostgreSQL Connection URIs
Decode the postgresql:// connection string — host, port, database, SSL mode, and the gotchas that cause connection refused at deploy time.