My Mysql notes
This is how you enable logging in MySQL
SET GLOBAL general_log=1;SET GLOBAL general_log_file='/var/log/mariadb.log';SET GLOBAL slow_query_log_file='/var/log/mariadb-slow.log';SET GLOBAL slow_query_log=1;
This is how you enable logging in MySQL
SET GLOBAL general_log=1;SET GLOBAL general_log_file='/var/log/mariadb.log';SET GLOBAL slow_query_log_file='/var/log/mariadb-slow.log';SET GLOBAL slow_query_log=1;
Docker has fundamentally changed how PHP applications are deployed. Modern Symfony, Laravel, and custom PHP systems increasingly rely on containers for local development, CI/CD pipelines, horizontal scaling, and production infrastructure consistency.
But Docker has also created a dangerous misconception inside the PHP ecosystem:
PHP-FPM has become the standard execution model for modern PHP infrastructure. Whether applications run on bare metal servers, inside Docker containers, or in Kubernetes clusters, PHP-FPM usually sits directly behind Nginx and processes every dynamic request entering the application stack.
Docker has become a standard deployment tool for PHP applications, especially in Symfony and modern microservice-based architectures. However, while Docker improves consistency and deployment speed, it does not automatically guarantee security.
Modern PHP infrastructure has evolved far beyond the traditional model of deploying a small application onto a single Linux server and exposing it directly to the internet.
Modern PHP applications rarely fail because of a simple SQL injection vulnerability or a missing input validation rule alone. Real-world compromises increasingly occur at the infrastructure layer through exposed services, weak deployment pipelines, leaked credentials, misconfigured containers, vulnerable dependencies, or poorly isolated application environments.
Choosing the right infrastructure automation platform is one of the most important decisions organizations make when scaling server management and DevOps workflows. Two of the most widely used configuration management tools are Puppet and Ansible.
SSL certificate problems are among the most common and frustrating issues administrators encounter when managing Puppet infrastructure. Puppet relies heavily on certificate-based authentication between agents and the Puppet server, and even minor certificate problems can prevent entire infrastructure environments from receiving configuration updates.
SSL Labs' A+ rating is the benchmark for a correctly hardened HTTPS configuration. Achieving it requires more than just installing a certificate — you need to restrict protocol versions, configure cipher suites appropriately, enable OCSP stapling, set strict HSTS headers, and tune session resumption.
Nginx's default configuration is conservative. The defaults for worker processes and connections will serve a low-traffic site without complaint, but they leave performance on the table for anything larger. Understanding what these settings do and how they interact lets you tune Nginx to use the hardware you have paid for.