Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a Getting Started section to the README.md file #1

Merged
merged 2 commits into from
Aug 23, 2017
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,24 @@ Argo is an open source container-native workflow engine for developing and runni
* Argo is cloud agnostic. Today we support AWS and GKE (alpha) with additional platforms coming soon.
* With Argo, you don’t need to install or learn other tools such as Jenkins, Chef, Cloud Formation... 

## Getting started

### Step 1: Download the argo binary

**Mac:** `curl -sSL -O https://s3-us-west-1.amazonaws.com/ax-public/argocli/latest/darwin_amd64/argo`

**Linux:** `curl -sSL -O https://s3-us-west-1.amazonaws.com/ax-public/argocli/latest/linux_amd64/argo`

```
chmod a+x ./argo
cp ./argo /usr/local/bin
```

### Step 2: Install argo

`argo cluster`


## History
VMs were a big improvement over physical servers when it came to dynamically provisioning and running applications. We found however, that VMs are too clunky and heavyweight for complex automation tasks and orchestrating distributed applications. When we started using containers for the first time, we were very excited by the potential of this lightweight and portable virtualization technology. We started creating a container-native platform for developing and running applications. We started with Mesos because that was the most stable platform for running distributed applicaitons at the time. A year later, we noticed that the Kubernetes community was growing faster and making more progress than any other container orchestration platform. We quickly switched to Kubernetes and haven't look back since :-)

Expand Down