New Interested in participating in the HCP Waypoint Private Beta Program? Apply here
  • Infrastructure
    • terraform
    • packer
  • Networking
    • consul
  • Security
    • vault
    • boundary
  • Applications
    • nomad
    • waypoint
    • vagrant
  • HashiCorp Cloud Platform

    A fully managed platform to automate infrastructure on any cloud with HashiCorp products.

    • consul
    • terraform
    • vault
    • packerbeta
    Visit cloud.hashicorp.com
  • Overview
  • Tutorials
  • Docs
  • CLI
  • Plugins
  • Community
GitHub
Download
    • Overview
      • Overview
      • Helm
      • Heroku, Vercel, etc.
      • Kubernetes
  • Getting Started
    • Overview
    • Compatibility Promise
    • Protocol Version Table
    • Release Notifications
      • Overview
      • Upgrade to 0.2.0
      • Upgrade to 0.3.0
      • Upgrade to 0.4.0
      • Upgrade to 0.5.0
      • Upgrade to 0.6.0
      • Upgrade to 0.7.0
      • Upgrade to 0.8.0

    • Install
    • Externally Built Images
    • Building Container Images
    • Helm Deployment
    • YAML-Free Deployment
    • YAML Directory Deployment
    • Resource Status
    • ConfigMaps and Secrets

    • Overview
    • Git Integration
    • Remote Operations
    • Overview
    • Build
    • Deploy
    • Release
    • Hooks
    • Labels
    • Workspace and Label Scoping
    • Overview
      • Overview
      • Input Variables
      • External Data
      • artifact
      • deploy
      • entrypoint
      • labels
      • path
      • workspace
      • Overview
      • Full Reference
      • Templating
      • Overview
      • Expressions
      • JSON Syntax
    • app
    • build
    • config
    • deploy
    • hook
    • plugin
    • registry
    • release
    • runner
    • url
    • use
    • variable
  • URL Service
  • Logs
  • Exec
    • Overview
    • Dynamic Values
    • Files
    • Internal Values
    • Workspace and Label Scoping
    • Overview
      • Overview
      • OIDC
      • Tokens
      • Overview
      • Maintenance
      • Production
      • Security
    • Express Server Install
    • Overview
    • Configuration
    • Profiles
    • On-Demand Runner
    • Additional Runners
  • Workspaces
  • Plugins
  • Triggers

    • Overview
      • Overview
      • Registering Plugin Components
      • Handling Configuration
      • Implementing the Builder Interface
      • Compiling the Plugin
      • Creating an Example Application
      • Testing the Plugin
    • Initializing the SDK
    • Passing Values Between Components
      • Overview
      • Authenticator
      • ConfigSourcer
      • Configurable
      • ConfigurableNotify
      • Builder
      • Registry
      • Platform
      • ReleaseManager
      • Destroy
      • Status
      • Default Parameters
      • Overview
    • Overview
    • Disable
    • Overview
    • GitHub Actions
    • GitLab CI/CD
    • CircleCI
    • Jenkins
  • Troubleshooting
  • Glossary

    • Overview
    • Architecture
    • Operation Execution
  • Roadmap
Type '/' to Search

»Waypoint Server

Waypoint utilizes a server to enable collaboration with other team members, storing operation history, and enabling functionality such as logs, exec, and more.

We've made it as easy as possible to install and run a Waypoint server using a single command: waypoint install. This automatically installs and configures the UI and local CLI to access the server and lets you start working with Waypoint immediately.

Note: Only one Waypoint server needs to be installed and run for any group of people using Waypoint together. If you are a day-to-day user of Waypoint with a group of people you may not need to install a server. In this case, see the documentation on connecting to a server.

»Connecting

To use the waypoint CLI, you must configure connection information.

Note: If you ran waypoint install to setup a server, the install command automatically configured the CLI for you to access the new server.

Waypoint uses something called a "context" to store server configuration information. The Waypoint CLI can be configured with multiple contexts to easily switch between multiple Waypoint servers (such as for work use, personal use, testing, etc.).

To create a context, use the waypoint context create command. This takes a set of flags to configure how to connect to the server. The example below configures a context:

$ waypoint context create \
    -server-addr=localhost:9701 \
    -server-auth-token=abcd1234 \
    -server-tls \
    -set-default my-server
$ waypoint context create \
    -server-addr=localhost:9701 \
    -server-auth-token=abcd1234 \
    -server-tls \
    -set-default my-server

The -set-default flag will set this as the default connection information. You can always switch contexts using waypoint context use or the WAYPOINT_CONTEXT environment variable.

»Verifying the Connection

To verify your CLI is connecting properly, use the waypoint context verify command. This will test that the default context can connect properly. It will output both the context tested and a success message if successful.

$ waypoint context verify
Successfully connected to the server using the "my-server" context.
$ waypoint context verify
Successfully connected to the server using the "my-server" context.

You can also specify a context name to test a specific context that isn't the default.

github logoEdit this page

Using Waypoint

The best way to understand what Waypoint can enable for your projects is to give it a try.

Waypoint tutorials
Waypoint documentation
Tutorial

Get Started - Kubernetes

Build, deploy, and release applications to a Kubernetes cluster.

View
Tutorial

Introduction to Waypoint

Waypoint enables you to publish any application to any platform with a single file and a single command.

View

Waypoint is maintained by HashiCorp, Inc.

View Code of Conduct
DocumentationCLI ReferenceTutorialsIntegrations
All systems normal