Introduction to Waypoint
Interested in talking with HashiCorp about your experience building, deploying, or managing your applications? Set up a time to chat!
Deploying applications in the DevOps landscape can be confusing with so many services, configuration files, and workflows to decode. As a developer, you just want to deploy your service. Waypoint can help with that.
Waypoint lets you publish any application to any platform with a single file and a single command:
waypoint up. This page describes how Waypoint works. When you are ready to try out Waypoint, follow the next tutorials to install, set up, and run Waypoint.
The standard Waypoint workflow involves one file,
waypoint.hcl, and two commands,
waypoint init and
waypoint.hcl file is a small configuration file that tells Waypoint how to build and release your application. You will write the configuration file in HCL syntax, which you might be familiar with if you use other HashiCorp products like Terraform.
waypoint init uses the configuration file and sets up your project in Waypoint. If you do not already have a
waypoint.hcl file for your application, Waypoint will automatically generate one with reasonable defaults as part of the initialization process.
A typical build, deploy, and release workflow requires many configuration files such as Dockerfiles, artifact publishing shell scripts, YAML resource files, and ingress configuration files.
You can create these files and use them with Waypoint, but it's not necessary as a single
waypoint.hcl file can provide the same functionality to dynamically package your application, publish it to a public or private container registry, configure application schedulers like Kubernetes or Nomad, and release your application to a public URL with HTTPS included.
Continue on to the installation tutorial by clicking on the Next button below and learn how to install the Waypoint CLI.