The pqrs project is taking its first steps. This initial activity, focused on establishing foundational documentation, highlights a critical aspect of sustainable software development.

The Situation

Many developers jump straight into coding, eager to see their applications take shape. Documentation often feels like an afterthought, a chore to be completed "later." This mindset frequently leads to projects starting without a proper `README.

Ever felt the dread of an upcoming application update? The pqrs project recently underwent a routine update, a seemingly simple task that, if not handled correctly, can lead to unforeseen issues. Updates are more than just adding new features; they're about maintaining health, security, and performance. But how do we ensure these updates are a smooth cruise rather than a rocky ride?

The Importance of Keeping Up

Think of your application like a complex machine, say, a high-performance

For many developers, the word 'deployment' can still evoke a slight cringe. Especially when it involves the venerable File Transfer Protocol (FTP). While modern CI/CD pipelines often leverage cloud platforms and containerization, countless projects, like pqrs, still rely on FTP for rapid, straightforward server updates. This post details how we transformed a manual, error-prone FTP deployment process into a robust, automated workflow using GitHub Actions.

The Situation

In our pqrs project, which leverages GitHub Actions for automated deployments, we recently identified and addressed a subtle inefficiency in our FTP deployment workflow. This small change has led to a cleaner and more performant CI/CD pipeline.

The Problem

Our ftp-deploy.yml GitHub Actions workflow included an npm ci step. While npm ci is an indispensable command for ensuring clean, reproducible dependency installations in build environments – especially when working with