A path through the garden
Cloud & systems.
How services fit together, run, and keep running.
Notes in this topic
25–36 of 45
- How an older WordPress VPS was put together
A retrospective on Nginx, PHP-FPM, MySQL, file ownership, backups, and certificate boundaries.
Cloud & systems - Inspecting an older CentOS network configuration
Interface inspection, network-scripts files, and the effect of restarting the network service.
Cloud & systems - Investigating Android Socket.IO polling timeouts
Separate transport timeouts, reverse-proxy upgrades, and certificate validation when diagnosing an old client.
Mobile & interfaces / Cloud & systems - Linux service state and boot-time enablement
A short reference separating running a service now from configuring whether it starts on boot.
Cloud & systems - MongoDB replica sets: members, authentication, and discovery
Reworking a MongoDB 4.4 notebook around topology, reachable member names, and connection discovery.
Cloud & systems - PM2 cluster mode and the state between workers
An older ecosystem configuration for two Node workers, with readiness, shutdown, and shared-state assumptions.
Cloud & systems - Point a short hostname at a canonical destination
An older Nginx redirect fragment, with DNS, redirect response, and HTTPS validation separated.
Cloud & systems - Proxying an application port through Nginx
A small historical reverse-proxy example with forwarding and WebSocket-upgrade headers.
Cloud & systems - Reading an older Firestore export and copy script
Schema-directed collection traversal, with the original script's naming and export-shape limitations made visible.
Cloud & systems / Tools & experiments - Reading an older Laravel Echo and Pusher integration
Connection state, event namespaces, and authorization roles in a historical Flutter example.
Mobile & interfaces / Cloud & systems - Reading an older MongoDB dump-and-restore upgrade notebook
Backup, installation, restore, and application verification are separate recovery steps.
Cloud & systems - Reading an older PostgreSQL pgbench experiment
Initialization, concurrent clients, and why two different benchmark workloads cannot be compared directly.
Cloud & systems