Romp Documentation

Romp Overview

  • Last Modified: 2019-09-17

Romp lets development and operations teams work closely together by enabling developers to specify exactly what infrastructure configuration their application requires so that operations can easily inspect these packages and deploy them in a simple but controlled manner.

Getting Started

Romp is primarily a command-line tool that lets you create and install packages. It’s really easy to get started:

  1. Download the Romp Installer
  2. Follow the Creating and Publishing an IIS Website tutorial

Romp and the Inedo Execution Engine

Romp uses the Inedo Execution Engine, which was created exclusively for infrastructure automation and orchestration. The Inedo Execution Engine lets you uses a combination of OtterScript, PowerShell, Text Templating, Operations, and Functions to accomplish virtually any kind of deployment or infrastructure configuration.

The easiest way to learn OtterScript is with the Visual Plan Editor. This drop-and-drop editor allows you to switch back-and-forth between visual and text modes to get a feel for the syntax and structure of the language pretty quickly.

You can install BuildMaster, Hedgehog, or Otter and then use them to help you construct these plans.

Romp and ProGet

Romp packages are extensions of universal packages, which means you can host your packages in a ProGet Universal Feed and use any of the UPack tools or libraries to interact with them.

Romp uses a package source to securely store a connection to a universal feed. You can also use the --source argument to specify a feed url (see common configuration).

Is this documentation incorrect or incomplete? Help us by contributing!

This documentation is licensed under CC-BY-SA-4.0 and stored in GitHub.

Generated from commit efc6666b on master