Getting Started

Below you will find guides and tutorials that will teach you how to use Dockbit and related systems. The documentation site is still work in progress, so if you find anything inaccurate, misleading or just missing, please open an issue or contribute.

What is Dockbit?

Dockbit is the continuous delivery platform built for teams. It integrates with all the tools you're using to deliver software, lets you connect them together and operate deployments from within your team chat (see Supported Chat Systems).

How does it work?

At the core of Dockbit is the Pipeline, which is a common term to describe a Continuous Delivery deployment pipeline. Essentially, Pipeline is a single app backed by a Git repository (see Supported Version Control Systems).

Pipeline consists of a number of stages, powered by Dockbit's Integrations, necessary to validate a piece of software from source control all the way through production.

Step-by-step

To get you started, let us walk you through creating a sample deployment pipeline for an Example Ember.js application and deploy it to AWS, along with any intermediary steps necessary to build and verify our application. We assume you've already signed up, created your Dockbit Team and added it to Slack.

Before creating any pipeline, it's beneficial to think a bit of the steps involved, which are in our case:

  • Pull Git repository with the source code.
  • Install Node.js and Bower application dependencies.
  • Build static site.
  • Deploy to AWS S3.

1. Create pipeline

Creating a Dockbit Pipeline is easy, but we will need a sample application. If you want to follow along, fork our Example Ember.js GitHub repository.

All you need to do now, is to click on the Create pipeline button in the top navigation, choose the forked repository and click Create:

  • The Name uniquely identifies this pipeline in your Team. It is also referenced in Slack when triggering deployments.
  • The Slack channel is the channel where you want to receive deployment notifications.

Getting Started - Step 1

Once the pipeline is created, Dockbit automatically sets up the GitHub deployment key and the webhook. As you may have noticed, the first step in the pipeline is preconfigured, which is there to pull any change in your repository.

2. Add stages

Now, we are ready to add the steps necessary to build, verify and deploy our application. Click on the plus icon in the Pipeline Editor and choose Action to bring up the integration form. To deploy our Ember.js application we will create two Dockbit Stages.

First, to build the static site with Node.js provider and second to deploy it with AWS s3_website provider. Fill up the Stage details as shown below and also remember to enter your own AWS access keys.

Getting Started - Step 2

Notice how we didn't need to install our app dependencies, nor configure credentials. The Dockbit Integrations are smart enough to detect and automatically configure them for us.

3. Deploy from Slack

It's time to deploy, right from Slack! Open up the Slack channel you've configured in the Pipeline Settings, instruct the Dockbit chatbot to deploy, and sit back-n-watch what happens.

Getting Started - Step 3

Yay! We now have a fully-automated deployment pipeline entirely operated via Slack 🤖

What is next?

Now that you have a taste of how to deploy your apps with Dockbit, there are a bunch of other exciting things you could do with it. Explore our evergrowing collection of Dockbit Integrations and extend your deployment process with testing, code analysis, and assessing security vulnerabilities. Or power up your pipelines with even more Dockbit Features, such as Auto Deploys, Deployment Queues, and Metrics. Happy shipping 🚀