OpenMiso is a community-driven fork of the Waypoint project. This project is not affiliated with, endorsed by, or connected to HashiCorp in any way.
OpenMiso is based on the last version of Waypoint released under the Mozilla Public License (MPL). We are currently in the process of removing all references, branding, and other elements associated with HashiCorp to ensure compliance with trademark and licensing rules.
We would like to express our gratitude to HashiCorp for creating and sharing Waypoint as an open-source tool, which has been a valuable resource for developers around the world. OpenMiso aims to build upon this foundation and continue its development in the spirit of openness and community collaboration.
Some resources below may still link to HashiCorp's website.
OpenMiso allows developers to define their application build, deploy, and release lifecycle as code, reducing the time to deliver deployments through a consistent and repeatable workflow.
OpenMiso supports a number of build methods and target platforms out of the box and more can be easily added via plugins:
- Cloud Native Buildpacks
- Docker
- Kubernetes
- AWS EC2 and ECS
- Azure Container Instances
- Google Cloud Run
- And many more...
OpenMiso runs on Linux, Mac OS X, and Windows.
A quick start guide is available on HashiCorp Developer. You can also find tutorials which cover topics ranging from getting started guides to more advanced usage.
- Getting Started
- Introduction
- Installation
- Docker
- Kubernetes
- Nomad
- Waypoint UI
- AWS ECS
- Azure Container Instance
- Google Cloud Run
Full, comprehensive documentation is available on HashiCorp Developer:
https://developer.hashicorp.com/waypoint/docs
Thank you for your interest in contributing! Please refer to CONTRIBUTING.md for guidance.
This repository contains a couple of different ways to automate installing the
required Golang packages needed to build Waypoint locally. You can either use
NixOS, or run make tools to setup the
required packages.
To run the entire test suite, you'll want to ensure that you've brought up
all the required containers used for testing. You can do this by leveraging
the existing docker-compose.yml file that's in the root directory of this
project:
$ docker-compose up
After running this, you should have a local Horizon container along with a few other services needed for running the tests:
$ make test
If you don't want to run the entire test suite, you can just run a singe test with go. For example, if you wanted to run the tests ListInstances, you would run:
$ go test -run ListInstances -v ./internal/server/singleprocess