No history yet

Setup and Cloud Storage

Beyond 'Final_v2.docx'

In any lab, keeping track of documents is crucial. You might have a folder full of files named protocol_v1.docx, protocol_v2_edits.docx, and the dreaded protocol_final_final.docx. It’s confusing, messy, and makes it hard to know which version is the correct one. What if you need to see what changed between versions, or who made a specific change? This is where version control comes in.

Think of version control as a professional tracking system for your files. Instead of saving dozens of nearly identical documents, you have one master file, and the system keeps a perfect, detailed history of every single change. It’s a reliable way to manage everything from Standard Operating Procedures (SOPs) to analysis scripts, ensuring your lab's data has integrity.

Version control is the lab notebook of the digital world: it’s what professionals use to keep track of what they’ve done and to collaborate with other people.

We're going to set up a simple version control system using two tools. First, we'll use Bitbucket to create a secure vault in the cloud for our files. Then, we'll use an application called SourceTree to connect that cloud vault to our computer, so we can manage everything with simple clicks instead of code.

Your Digital Lab Vault

Our first step is to set up the remote storage, which is like a central, secure locker for our lab's documents. We’ll use a service called Bitbucket for this. It’s free for small teams and perfect for our needs.

  1. Go to the Bitbucket website and sign up for a new account.
  2. Once you're logged in, it's time to create your first repository. Think of a repository (or 'repo') as a single, tracked project folder. You might create one for a specific experiment, or one for all of your lab's general SOPs.

To create a repository:

  • Click the '+' icon on the left-hand menu and select 'Repository'.
  • Give your repository a name, like lab-protocols.
  • You can add a description if you like, but for now, just click 'Create repository'.

That's it. You've just created a secure, version-controlled folder in the cloud. This is now the central 'source of truth' for whatever project you decide to store here.

Lesson image

Connecting to Your Computer

Now we need a way to link that cloud repository to your own computer. We'll use SourceTree, a visual tool that shows you your files, their history, and lets you manage everything with buttons.

First, download and install SourceTree from its official website. During the installation, it will ask you to connect to an account. Choose Bitbucket and log in with the credentials you just created. This links the application on your computer directly to your cloud vault.

With SourceTree installed and linked, we can now bring a copy of our cloud repository down to our computer. This process is called cloning.

When you clone a repository, you're not just downloading the files. You're downloading the entire project history. This creates a local repository on your computer that is a perfect mirror of the remote repository on Bitbucket.

To clone your repository using SourceTree:

  1. Open SourceTree. You should see a list of your remote repositories from Bitbucket.
  2. Click the 'Clone' button next to the repository you created (e.g., lab-protocols).
  3. Choose a destination path on your computer. This is the folder where your project will live locally. A good spot is your Documents folder.
  4. Click 'Clone'.

SourceTree will now download the repository to your computer. If you navigate to the folder you selected, you'll see it there. It might be empty for now, but it's fully connected to its remote counterpart on Bitbucket.

Clone

verb

The process of creating a local copy of a remote repository, including all its files and history.

You now have two linked versions of your project: the remote one on Bitbucket, which acts as the main backup and collaborative hub, and the local one on your computer, where you'll do your actual work. In the next section, we'll learn how to add files and save our changes using this new setup.