Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

Nobody can release a new version of my app

Short answer

When a release lives in one person's head or on one laptop, your app cannot be updated safely. Gather every account, key and note you can find, and do not rebuild anything yet. An engineer can then turn the release into a written, repeatable process that does not depend on one person.

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

Does this sound like your situation?

  • My developer left and nobody can publish an update.
  • Releases only work from one laptop.
  • I do not know where the server password or the keys are.
  • A small fix is delayed because releasing is scary.
  • There are no written steps for putting the app live.

Why does this happen?

  1. The release was never written down

    A quick launch skips documentation. The steps then exist as habits of the person who did them.

  2. The steps run from a personal machine

    Scripts, keys and settings stay on one laptop. If it is lost or the person leaves, the process goes with it.

  3. Secrets are scattered

    Server logins, signing keys and API tokens are in chat messages or personal accounts.

  4. Automation can make a release repeatable

    GitHub documents building a continuous deployment pipeline that runs tests before deploying, can require approval for production through environments, and can limit the pipeline to one deployment at a time.

What can I do about it today?

  1. Ask for the code repositoryFind out where the source code is kept and whether your company owns that account.
  2. Collect accounts and notes in one placeHosting, domain, app stores, email and any notes the developer left. Share them with two people in your company.
  3. Do not rebuild the server or delete anythingOld setups often hide steps nobody remembers. Leave it running as it is.
  4. Ask the previous developer for a recorded walkthroughA screen recording of one real release is valuable, even if it is rough.
  5. Do not post passwords in chatShare access by adding people to accounts, not by sending passwords.

When should I bring someone in?

  • Nobody can release a fix and customers are affected.
  • The only person who knew has left and left no access.
  • You do not have the source code.

How do I handle it?

  1. Find the real release pathI trace how the app gets from code to the live server or store, from whatever is left.
  2. Do a release on a copy firstI prove the steps on a copy, without touching production.
  3. Write the steps downA short, plain runbook anyone technical can follow.
  4. Automate and keep secrets safeThe release runs from a pipeline you own, with keys stored as secrets, and a tested way back.

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?

Can this be fixed without the old developer?

Often yes, if the source code and server access exist. Without the code, it is a different problem.

Do I need a pipeline?

Not necessarily, but a written, repeatable release is the minimum.

How long will it take?

It depends on what is left. I give a written scope after a first look.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. 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.