Deploying changes by manually uploading files over FTP works until it doesn’t — an overwritten file, no record of what changed or when, no way to cleanly undo a bad deployment. Git-based deployment tracks every change and lets you push updates (and roll them back) in a controlled, repeatable way instead.
Version control (Git) deployment setup
Manual FTP uploads replaced with version-controlled, reversible Git deployment.
- 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
- Hosting access that supports Git-based deployment (many modern hosts do; we’ll confirm yours)
- A Git hosting service preference, if you have one (GitHub, GitLab, Bitbucket), or we can recommend one
- Confirmation of your current deployment process, so we know what we’re replacing
This or something else?
| You want a version-controlled, Git-based deployment process set up | This fix covers it |
| Your site broke after a manual deployment and needs fixing now | Local to live deployment repair, the immediate fix first |
| You want a staging environment as well, to test before deploying | Staging environment creation & sync, a strong complement to this |
| You’re moving to a new host entirely, not changing your deployment method | Host-to-host migration – single site |
What we do
- Confirm your hosting supports Git-based deployment, or recommend hosting that does
- Set up a Git repository for your site’s code, if one doesn’t already exist
- Configure automated or triggered deployment from the repository to your hosting
- Test the deployment process with a real, low-risk change
- Document how to make and deploy future changes using this new process
- Confirm you or your team can comfortably use the new workflow
What is included
- A configured, tested Git-based deployment process
- A working repository connected to your hosting
- Verified deployment of a real test change
- A written guide on using the new process going forward
Not included
- Hosting migration, if your current host doesn’t support this and you need to move
- Ongoing code review or version control training beyond initial setup
- Setting up a staging environment, a separate, complementary fix
- Resolving issues in your existing codebase unrelated to the deployment process itself
Questions about this fix
Do I need to know Git myself to benefit from this?
Not deeply — we set up the process and document the specific, repeatable steps you or your developer need to follow, which is considerably simpler than needing to understand Git comprehensively.
Will this let me undo a bad deployment easily?
Yes, that's one of the main benefits — a version-controlled deployment keeps a clear history, making it straightforward to roll back to a previous, known-good state if something goes wrong.
Does my current hosting support this, or would I need to switch?
Many modern hosts do support Git-based deployment — we confirm this specifically for your current setup and only recommend switching if it's genuinely not supported.
Is this overkill for a small site with infrequent changes?
It depends on how much you value having a clean history and easy rollback — even infrequent changes benefit from not risking an untracked, manual overwrite, though the case is strongest for sites that change often.
Can multiple people deploy changes safely with this set up?
Yes, that's another genuine advantage — a shared, version-controlled process handles multiple contributors far more safely than everyone manually uploading files independently.
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.