Getting Started with GitLab - Blueprint

Updated by @KeithResar on May 14, 2015

Description

GitLab Logo

After reading this article, the reader should feel comfortable deploying the GitLab stack (version 7.10.1-0) by Bitnami.

Bitnami has integrated their GitLab stack with the CenturyLink Cloud platform with a single-click deploy solution. The purpose of this KB article is to help the reader take advantage of this integration to achieve rapid time-to-value for this GitLab solution.

The GitLab open source edition is a developer tool that allows users to collaborate on code, create new projects, manage repositories, and perform code reviews. When using GitLab, users can keep their code on their own servers, either in the cloud or on-premise. For additional peace of mind, the free community edition even features enterprise-grade features such as a mature user permissions scheme and support for high availability. This GitLab stack is bundled with GitLab CI, a continuous integration server. Just point your projects at the CI server and automate all your tests.

Audience

CenturyLink Cloud Users

Deploying GitLab on a New Server

GitLab is available as a Blueprint for deployment on a new server.

Steps

  1. Locate the Blueprint in the Blueprint Library.

    • Login to the Control Portal. From the Nav Menu on the left, click Orchestration > Blueprints Library.
    • Search for 'GitLab on Linux' in the keyword search on the right side of the page.
  2. Click the deploy blueprint button.

  3. Set Required parameters. Set the following parameters in addition to those associated with your server itself (password, network, group, etc.):

    • Apache server SSL port - default 443
    • Redis port - Redis Server port default 6379
    • Apache server port - default 80
    • Service Password - Provide service password 6 chars or more
    • User's name - Users Name
  4. Review and Confirm the Blueprint.

  5. Deploy the Blueprint.

    • Once verified, click the deploy blueprint button. You will see the deployment details stating the Blueprint is queued for execution.
    • This will kick off the Blueprint deploy process and load a page where you can track the deployment progress. Deployment will typically complete within five minutes.
  6. Deployment Complete.

    • To monitor progress, click Queue from the Nav Menu on the left.
    • Once the Blueprint has finished executing on your server you may access GitLab by navigating to your server via http.
  7. Enable public access (optional).

    • Servers are built using private IPs only with access with client or IPSEC VPN. For inbound access from the Internet add a public IP to your master server.

    Adding a public IP to your virtual machine

Deploying GitLab on an existing server (alternate option)

GitLab is available as a Blueprint Package for deployment on an existing server based on your own sizing requirements or to support more advanced configurations such as customized Blueprint Workflows to repeatably deploy multiple stacks on the same machines

Steps

  1. Deploy or Identify an Existing Server.

  2. Select to Execute the Package on a Server Group.

    • Packages can be executed on one more more servers in a group. Search for the public script package named Install GitLab on Linux.
    • See the using group tasks to install scripts on groups KB for more information on how to complete the next few steps.
  3. Set Parameters. Set the following parameters:

    • Apache server SSL port - default 443
    • Redis port - Redis Server port default 6379
    • Apache server port - default 80
    • Service Password - Provide service password 6 chars or more
      • User's name - Users Name
  4. Deploy the Blueprint.

    • Once verified, click the execute package button. You will see the deployment details stating the Blueprint is queued for execution.
    • This will kick off the Blueprint deploy process and load a page where you can track the deployment progress. Deployment will typically complete within five minutes.
  5. Deployment Complete.

    • To monitor progress, click Queue from the Nav Menu on the left.
    • Once the Blueprint has finished executing on your server you may access GitLab by navigating to your server via HTTP.
  6. Enable public access (optional).

    • Servers are built using private IPs only with access with client or IPSEC VPN. For inbound access from the Internet add a public IP to your master server.

    Adding a public IP to your virtual machine

Pricing

The costs listed above in the above steps are for the infrastructure only.

About Bitnami

CenturyLink Cloud works with Bitnami to provide open source software integrations to its customers. Bitnami is a library of popular server applications and development environments that can be installed with one click, either in your laptop, in a virtual machine or hosted in the cloud. Bitnami takes care of compiling and configuring the applications and all of their dependencies (third-party libraries, language runtimes, databases) so they work out-of-the-box. The resulting packaged software (a 'stack') is then made available as native installers, virtual machines and cloud images. These Bitnami application packages provide a consistent, secure and optimized end-user experience when deploying any app, on any platform.

Frequently Asked Questions

Who should I contact for support?

How do I access GitLab for the first time?

  • Nearly all Bitnami stacks can be accessed and configured by navigating to your server with a web browser.

Customer Support

Can’t find what you need?
Give us a call.

1.888.638.6771

M – F, 8am to 6pm