Before getting started with Boundary, it's important to understand a few key concepts. Please consult our Boundary concepts page to familiarize yourself with Boundary's architecture, and terminology.
The examples in Getting Started all revolve around running in
dev mode. There are a few requirements for running dev mode:
- Docker is installed
- A route to download the Postgres Docker image is available or a local image cache is available
- A Boundary binary in your
»What is Dev Mode?
Dev mode is an all-in-one installation method for getting started with Boundary quickly. As the name implies, dev mode is not a production installation method, but instead a way to get Boundary running with a Postgres database easily. Do not use dev mode in a production environment, see Production Installation section for production ready deployment methods.
Dev mode brings up a fully functioning instance of Boundary, including:
- A controller server
- A worker server
- A Postgres database
These components should all be considered ephemeral - no data persistence occurs across dev mode restarts. Along with these external components, dev mode also creates several resources within Boundary to make it easier and faster to connect to your first target:
- A org scope and a project scope with a default ID of
- An auth method with a random login name and password with a default auth method ID of
- A static host catalog with a default ID of
- A static host and host set with default ID's of
- A TCP target with a default ID of
The default ID suffixes are overridable or can be randomly generated, and there are many other dev mode controls. To see a complete list of these override flags, consult
boundary dev -h.
If you plan on provisioning a large number of resources in dev mode, it's strongly recommended that users leverage our Terraform Provider for Boundary for managing configuration of Boundary. This will simplify starting up and shutting down your Boundary dev instance.