A useful change history
Record the reason for a change alongside the files involved. A clear history makes reviews and later investigations easier.
Git version control
Good changes deserve a clear history.
Keep track of website code, review changes and plan releases with version control. Bring your developer and your hosting requirements into the same conversation.
The practical picture
Know what changed, and why.
Git records changes to tracked files. It helps a developer compare versions and work on a change separately before bringing it into the main codebase. 20i provides integrated Git tools on its hosting platform.
Space to develop
Branches support work on separate changes. Agree how code is tested and approved before it is deployed to a public website.
A controlled release
Check which Git and deployment tools your hosting configuration exposes. Repository access, application builds and database changes still need a release plan.
The details that matter
A sensible release workflow.
Review a focused change
Keep a change small enough for the developer to understand and verify. Use meaningful commit messages and a review step appropriate to the impact on the website.
Separate secrets and data
Keep passwords, keys and private customer information out of repositories. Use the agreed server-side configuration and a backup arrangement for data that is not tracked in Git.
Made for the working day
Keep the history. Protect the business data.
Version control is useful for application code, but it is not a complete website backup. Orders, enquiries, uploaded media and configuration can live outside the repository. Keep credentials out of source control and agree how those other parts of the website will be protected before a deployment.
Talk through your requirements
A little clarity
Git version control, explained.
Useful answers before you decide. For anything specific to your website, let’s talk it through.
Does Git replace website backups?
No. A repository normally contains selected files, rather than every database record, upload and service setting needed to recover the website.
Can my developer keep using their existing repository?
Tell us how your developer currently deploys and which repository provider they use. We will check the proposed workflow against the chosen hosting tools and access permissions.
Does reverting a commit reverse every website change?
No. A code change and a database change can have different recovery steps. Check the application and preserve newer business records before rolling anything back.
Let’s find the right fit.
Start with your business. We will help with the hosting.