Getting Started
- Overview
- Installation
- Configuration
- Quickstart
- Processes
- Projects
- Forms
- Scripting
- Security
- Tasks
- Organizations and Teams
- Policies
- JSON Store
- Node Roster
- Development
Processes (v2)
Processes (v1) - DEPRECATED
Triggers
Console
API
- API Key
- Checkpoint
- Form
- JSON Store
- Node Roster
- Organization
- Policy
- Process
- Project
- Repository
- Role
- Secret
- Team
- Template
- Trigger
- User
Plugins (v2)
- Akeyless
- Argo CD
- Ansible
- Asserts
- Concord
- Confluence
- Crypto
- Datetime
- Docker
- Files
- Git and GitHub
- Gremlin
- HashiCorp Vault
- HTTP
- Jenkins
- Jira
- JSON Store
- Key Value
- LDAP
- Lock
- Mocks
- MS Teams
- Node Roster
- Puppet
- Resource
- S3
- Slack
- Sleep
- SMTP
- Taurus
- Terraform
- XML
- Zoom
Plugins (v1) - DEPRECATED
- Akeyless
- Ansible
- Concord
- Confluence
- Crypto
- Datetime
- Docker
- Git and GitHub
- Gremlin
- HashiCorp Vault
- HTTP
- Inventory
- Jenkins
- Jira
- JSON Store
- Key Value
- LDAP
- Lock
- MS Teams
- Node Roster
- Packer
- Puppet
- Resource
- S3
- Slack
- Sleep
- SMTP
- Taurus
- Terraform
- XML
- Zoom
Templates
CLI
Community
Home > docs > getting started > install > Installation using Vagrant
Installation using Vagrant
Requires Vagrant 2.2+.
To start Concord using Vagrant:
$ git clone https://github.com/walmartlabs/concord.git
$ cd concord/vagrant
$ vagrant up
It starts Concord using the latest available Docker images. OpenLDAP running in a container will be used for authentication.
The vagrant up command might take a while, typically ~5 minutes, depending
on the internet connection.
Refer to the README.md file for more details.
