We build a deployment script automating how code changes move from your development environment to live — and unlike a scheduled task running silently in the background, this is something your team invokes deliberately each time you deploy, though it still needs an owner: someone who understands what it does and can update it as your site’s environment changes.
Deployment script creation
A deployment script your team runs deliberately — documented so it's not a black box later.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
What we need from you
- Confirmation of your current development, staging, and live environment setup
- A clear spec of the deployment steps the script should automate
- Access sufficient to build and test the script across your environments
This or something else?
| You want a script automating your deployment process from development to live | This fix covers it |
| You want a fully automated, version-controlled deployment process set up, a related but broader concept | Version control (Git) deployment setup, in the Backups, Staging & Migration Ops category, if that’s genuinely what you need |
| You want an existing, broken deployment process fixed, not a new script created | Local to live deployment repair, in the Backups, Staging & Migration Ops category |
| You want a one-time migration between hosts, not a repeatable deployment script | Host-to-host migration – single site |
What we do
- Confirm the exact deployment steps needing automation
- Build the deployment script to handle those steps reliably
- Test the script across a realistic deployment scenario
- Verify it handles common edge cases (a failed step, a partial deployment) sensibly
- Document exactly what the script does and how to run it
- Provide written documentation on maintaining it as your environment evolves
What is included
- A deployment script automating your specified steps
- Tested across a realistic deployment scenario
- Sensible handling of common edge cases
- Written documentation on running and maintaining it
Not included
- Ongoing use or execution of the script on your behalf as a standing service — your team runs it, we build and document it
- Updating the script indefinitely as your environment changes, unless engaged separately at that time
- Setting up a broader, fully automated CI/CD pipeline, a larger, separate project if that’s genuinely what you want
- Fixing an unrelated, pre-existing deployment issue not covered by this new script
Questions about this fix
Who actually runs this script once it's built?
Your team, whenever you're ready to deploy — this isn't automation running silently in the background on a schedule, it's a tool your team invokes deliberately each time, which is a meaningfully different kind of ownership than a scheduled task.
What happens if my hosting environment changes significantly later?
The script is built against your current environment's specifics, so a significant change (a different host, a different server configuration) could require it to be updated — that's a separate, follow-up piece of work at that time, not something covered indefinitely by this initial build.
Does this replace needing to understand deployment at all?
No, it automates the repetitive steps, but your team still needs to understand roughly what it does and when to run it — we document this specifically so it's not a mysterious black box.
What if a deployment using this script goes wrong partway through?
We test for sensible handling of common failure points, and document what to check if something does go wrong, though no deployment automation can guarantee perfect behaviour under every possible failure scenario.
Is this the same as setting up Git-based deployment?
Related but more limited in scope — this automates specific deployment steps you define; Git-based deployment is a broader, more structured approach to version-controlled deployment, which is a separate, larger fix if that's what you're actually after.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.