Drycc Workflow is an open source Platform as a Service (PaaS) that adds a developer-friendly layer to any Kubernetes cluster, making it easy to deploy and manage applications.

Drycc Workflow is the second major release (v2) of the Drycc PaaS. If you are looking for the CoreOS-based PaaS visit https://github.com/drycc/drycc.

To get started with Drycc Workflow please read the Quick Start Guide.

Visit https://drycc.cc for more information on why you should use Drycc Workflow or learn about its features.

This repository contains the source code for Drycc Workflow documentation. If you're looking for individual components, they live in their own repositories.

Please see below for links and descriptions of each component:

• controller - Workflow API server
• builder - Git server and source-to-image component
• dockerbuilder - The builder for Docker based applications
• slugbuilder - The builder for slug/buildpack based applications
• slugrunner - The runner for slug/buildpack based applications
• fluentd - Backend log shipping mechanism for drycc logs
• postgres - The central database
• registry - The Docker registry
• logger - The (in-memory) log buffer for drycc logs
• monitor - The platform monitoring components
• router - The HTTP/s edge router
• minio - The in-cluster, ephemeral, development-only object storage system
• nsq - Realtime distributed messaging platform
• workflow-cli - Workflow CLI drycc
• workflow-e2e - End-to-end tests for the entire platform
• workflow-manager - Manage, inspect, and debug a Workflow cluster

We welcome your input! If you have feedback, please submit an issue. If you'd like to participate in development, please read the "Working on Documentation" section below and submit a pull request.

The Drycc project welcomes contributions from all developers. The high level process for development matches many other open source projects. See below for an outline.

• Fork this repository.
• Make your changes.
• Submit a pull request (PR) to this repository with your changes, and unit tests whenever possible.
  • If your PR fixes any issues, make sure you write Fixes #1234 in your PR description (where #1234 is the number of the issue you're closing).
• The Drycc core contributors will review your code. After each of them sign off on your code, they'll label your PR with LGTM1 and LGTM2 (respectively). Once that happens, a contributor will merge it.

The documentation site requires either a local installation of MkDocs or access to Docker.

Install MkDocs and required dependencies:

make deps

To build the documentation run: make build or make docker-build.

To serve documenation run: make serve or make docker-serve.

Then view the documentation on https://localhost:8000 or https://DOCKER_IP:8000.