We deploy by hand and it keeps breaking
Someone on your team copies files to a server, or runs a list of commands from memory. Most days it works. Now and then it takes the site down, and getting back to the last working version is guesswork. If that person is on holiday, nobody releases anything.
What I'd do
- Write down how a release happens today, including the steps that live in one person's head.
- Turn it into a deployment that runs the same way every time, straight from where your code is kept, with one click.
- Add a way back: a tested step that returns you to the previous version.
- Show your team how it works, so more than one person can release.
What you get at the end
A deployment anyone on the team can run, a written rollback, and a short note explaining what I changed and why. Everything lives in your own accounts.
What it costs
Writing down how you release today, and what it would take to automate it, is a small job, from £500. Setting up the deployment itself is quoted as a fixed price once I've seen it. Either way you know the total before you say yes.
I take this on as a single job at a fixed price, or as part of regular days each month or a contract. Get in touch.