It's been said that all of software development is just debugging at increasing levels of precision. And debugging is the process of figuring out what happened in a given set of circumstances.

The problem is that as software developers, we often only have part of the puzzle when debugging. We use Git, so we know how to control for code versions. We use Docker, so we know how to control for most app environment variables. But state is equally important, as many bugs manifest only based on a combination of code and data, and state is hard to control across environments.

That's why we set out to make sharing error state between people and environments as easy as, well, sharing code.

Problems with debugging today:

  • Error state is hard to move from CI to local environment
  • Can’t easily share error state with colleagues
  • Bug reports with only app version are incomplete
  • Debugging against different data versions is complex to manage
QA that devs will love

QA that devs will love

QA people are great at breaking things. It’s their job. But as a developer trying to fix that bug, things aren’t always so easy. Even well-intentioned bug reports often don't come with test data used during the test. This makes developers have to search around, sometimes randomly and always frustratingly, to figure out how to recreate issues seen in QA.

With FlockerHub, the QA team can provide their developers a link to the Docker volume used as part of the test to induce appearance of the bug, ensuring that engineering has everything they need to isolate the issue. Next thing you know, it’s a dev+QA love fest.

Banging your head against a bug? Ask for help. Easily.

We all need help sometimes. The problem isn’t that our colleagues won’t help. Often, they just can’t.

Many times when we ask for help, our peers struggle to recreate a problem on their laptop because the bug depends on the state of the database which they usually don’t have. With FlockerHub, you can share error state as easily as you can share code or containers. This makes it easy for you to ask for help, and easy for others to give it to you.

Banging your head against a bug?  Ask for help. Easily

The best bug reports come with data

Imagine if each of your bug reports or build failures came not only with the code branch and Docker containers used, but with a link to the downloadable Docker volume so you could truly recreate the failure locally.

With FlockerHub, this dream isn’t pie in the sky. It is as easy as programmatically snapshotting your Docker volumes and pushing them to FlockerHub. Then, when it’s time to debug, you can pull them locally or into a test environment and have everything you need to swat that pesky bug.

Signup for FlockerHub today

Learn more about FlockerHub and Fli

Push and pull data snapshots

The basics of how to move data with Fli and FlockerHub.

Creating volumes

Learn how to create a data volume using Fli, the FlockerHub CLI.

Updating object metadata

Learn how tag your data snapshots with user-defined attributes so they are easy to find and manage.

How to setup Fli with your ZPool

Learn how to set up a local storage pool to store and take snapshots.

Got a question?

Thanks for your email, we'll be in touch shortly