Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My releases are copied to the server by hand every time

Short answer

Hand-made releases depend on one person typing the right commands in the right order, so mistakes and missing steps are likely. Automating the release makes it repeatable and recorded, but write the manual steps down first and keep a way back.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • My developer uploads files to the server by hand.
  • Releases take hours and one forgotten step breaks the site.
  • Nobody else can release.
  • I do not know which version is live.
  • A release once overwrote a fix someone had made on the server.

Why does this happen?

  1. The steps are in one person's head

    Manual steps vary from run to run and are easy to skip.

  2. No record of what was deployed

    Without a log, you cannot tell which version is live or what changed last.

  3. Changes made directly on the server

    Edits on the live machine never reach the code, so the next release can erase them.

  4. Setting up automation was postponed

    It takes effort at the start, so a manual routine that works lingers.

What can I do about it today?

  1. Ask for the steps in writingRequest every step of a release, in order, with where the files and logins are.
  2. Ask which version is liveAsk for the exact version number or date now live and where that record is kept.
  3. Stop edits directly on the serverAgree that fixes go through the code first, so they are not lost.
  4. Get a backup before each releaseAsk that a backup is taken and its location noted.
  5. Do not rush a full automationDo it step by step, starting with the most error-prone part.

When should I bring someone in?

  • Only one person can release.
  • A release has broken the live site more than once.
  • You need to release often, for example weekly or more.

How do I handle it?

  1. Document what happens todayI record the manual steps and the places where mistakes could occur.
  2. Script the repeatable partsSteps are turned into a script that does the same thing each time.
  3. Run it automaticallyThe script runs from the code repository on each approved change.
  4. Add checks and a rollbackA quick check follows each release, and a tested way back is kept.
  5. Keep a release logYou can see what went live, when and who approved it.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

What does CI/CD mean?

Roughly, checks and releases that run automatically when code changes, instead of by hand.

Does automating mean no human approval?

No. A person can still approve each release. Only the repeatable steps are automated.

Is it worth it for a small app?

If releases are frequent or errors costly, yes. A simple script can be enough to start.

How was this page made?

I drafted this page with AI assistance. It is general guidance for business owners, not advice for your own system. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.