midvision/rd repository overview

Feature overview:

This image contains the RapidDeploy framework server and agent which is free to use for up to 10 target nodes. RapidDeploy can be used to manage your deployments and releases to any target via SSH or using an agent. RapidDeploy features:

• Full Web UI based application with integrated database with no initial configuration needed;
• Release pipelines and server task orchestrations both editable via your web browser 'drag and drop' canvas;
• Task based orchestration with hundreds of built-in tasks + manage & run your own scripts;
• Deploy to any servers, including full integrations to the popular cloud infrastructures such as AWS and Azure;
• Easily and automatically pull in external resources from anywhere (remote file/folder, web, SCM or artefact repository) to include in your release;
• Full release versioning within the tool, with drill-down comparison capability for project release versions;
• Plug in architecture with integrations for popular build, SCM, artefact repository tools and to aid deployments to application servers, middleware, docker, databases etc;
• Real time release and deployment log viewer, full audit and approvals logs;
• Release pipeline failure branches, orchestration failure branches, rollback pipelines;
• Replay, rerun, restart jobs from last failure functionality;
• Full security model with fine grained access controls and integration with LDAP, AD, SSO;
• Easily cluster RapidDeploy for load balancing and failover;
• Web UI, Command line and Web services interfaces;
• Full unattended deployment, calendar scheduling and blackout period functionality;
• Reporting dashboard with drill-down capability;
• Configure RapidDeploy to use any enterprise database such as Oracle or DB2 if required.

Download the image and run the container:

• Pull RapidDeploy latest version from docker hub using: docker pull midvision/rd
• Make the directory where the RapidDeploy files that will survive an upgrade are located: mkdir -p ~/dockershare/external/rd
• Run the container (name will be midvision_rapiddeploy): docker run -t -d -p 9090:9090 -v ~/dockershare/external/rd/libraries:/rd/libraries -v ~/dockershare/external/rd/resources:/rd/resources -v ~/dockershare/external/rd/snapshots:/rd/snapshots -v ~/dockershare/external/rd/logs:/rd/logs -v ~/dockershare/external/rd/projects:/rd/projects -v ~/dockershare/external/rd/db:/rd/users/root -v ~/dockershare/external/rd/buildstore:/rd/buildstore -v ~/dockershare/external/rd/promotionstore:/rd/promotionstore -v ~/dockershare/external/rd/users:/rd/users --name "midvision_rapiddeploy" midvision/rd

RapidDeploy URL:

Once you run the container, you can log in to RapidDeploy. The RapidDeploy URL will be http://YOUR-IP:9090/MidVision⁠ (Make sure the 9090 port is open on any firewalls)

Log in to the Web Console:

For a newly installed RapidDeploy instance, the following credentials can be used to log in to the Web Console as the super user. Be sure to change the password!

Username: mvadmin
Password: mvadmin

Getting Started:

When the container is started, the framework server running Java 8 in Tomcat 9 and a (local) RapidDeploy agent will be started. Logs, database and project volumes are exposed.

You can find a step-by-step tutorial introducing RapidDeploy concepts and along the way creating your first project, target server definition, resource and target environment definition here⁠. There are instructions for configuring⁠ and installing plugins⁠ into RapidDeploy on our web site⁠. Comprehensive RapidDeploy documentation can be found in our how to guides⁠.

Information about available plugins for RapidDeploy can be found on the plugins page⁠.

You can also download and install some blueprints⁠ to get started with specific tasks.

Connecting to remote servers:

The RapidDeploy container runs a local agent by default for you to use to run a Hello World deployment or more generally for local jobs. You can configure RapidDeploy to deploy to any server running SSH or you can install an agent on the server. Agents for linux, windows platforms etc can be downloaded from here⁠.

By default these agents all ship with an inbuilt Java 1.8 JRE. However, you can choose to use any other (Java 1.8+) JRE by setting JAVA_HOME appropriately.

For any further information, please visit our website⁠

Upgrading to a later version of RapidDeploy:

To upgrade (In this example we're upgrading from RapidDeploy 5.0.20 to 5.0.21. Replace 5.0.21 with the actual version you are upgrading to):

• Pull the new version from docker hub using: docker pull midvision/rd:5.0.21
• Stop the currently running RapidDeploy 5.0.20 container: docker stop midvision_rapiddeploy
• Rename the container: docker rename midvision_rapiddeploy midvision_rapiddeploy_5020
• Run the new container using the new image: docker run -t -d -p 9090:9090 -v ~/dockershare/external/rd/libraries:/rd/libraries -v ~/dockershare/external/rd/resources:/rd/resources -v ~/dockershare/external/rd/snapshots:/rd/snapshots -v ~/dockershare/external/rd/logs:/rd/logs -v ~/dockershare/external/rd/projects:/rd/projects -v ~/dockershare/external/rd/db:/rd/users/root -v ~/dockershare/external/rd/buildstore:/rd/buildstore -v ~/dockershare/external/rd/promotionstore:/rd/promotionstore -v ~/dockershare/external/rd/users:/rd/users --name "midvision_rapiddeploy" midvision/rd:5.0.21

Please be aware that if you store any RapidDeploy resources in the RapidDeploy container but outside of the exposed volumes, these resources will NOT be preserved following an upgrade.

Exposed volumes:

• /rd/projects is the location of the RapidDeploy project data stored on disk.
• /rd/snapshots is the location of the RapidDeploy snapshot data stored on disk.
• /rd/resources is the location of the RapidDeploy external resource data (location) stored on disk.
• /rd/libraries is the location of the RapidDeploy library data stored on disk.
• /rd/logs is the location of the RapidDeploy log files
• /rd/users/root is the location of the HSQL Database file
• /rd/users is the location of the RapidDeploy security role files
• /rd/buildstore is the location of the deployment packages when using the (default) filesystem based artifact repository plugin
• /rd/promotionstore is the location of the promotable deployment packages when using the (default) filesystem based artifact repository plugin

Please be aware that if you store any RapidDeploy resources in the RapidDeploy container but outside of the exposed volumes listed above, these resources will NOT be preserved following an upgrade. Therefore please ensure any paths to resources you create in RapidDeploy that are on the local filesystem inside the container, these must be either in one of the exposed volumes above, or you need to add your own exposed volume which you should add to the Docker run command.