Upgraded apache-airflow to 1.10.5 to address the database migration issue https://issues.apache.org/jira/browse/AIRFLOW-6046. Change-Id: Ib8678cddb2deb4f5ef944d026e0d2633a326d9cc
|1 year ago|
|charts/shipyard||1 year ago|
|doc||1 year ago|
|etc/shipyard||3 years ago|
|images||1 year ago|
|src/bin||1 year ago|
|tools||1 year ago|
|.dockerignore||3 years ago|
|.editorconfig||3 years ago|
|.gitignore||3 years ago|
|.gitreview||2 years ago|
|.zuul.yaml||1 year ago|
|LICENSE||3 years ago|
|Makefile||1 year ago|
|README.rst||3 years ago|
|requirements.readthedocs.txt||3 years ago|
|tox.ini||3 years ago|
Shipyard adopts the Falcon web framework and uses Apache Airflow as the backend engine to programmatically author, schedule and monitor workflows.
Find more documentation for Shipyard on Read the Docs.
The current workflow is as follows:
Note: This project, along with the tools used within are community-based and open sourced.
The goal for Shipyard is to provide a customizable framework for operators and developers alike. This framework will enable end-users to orchestrate and deploy a fully functional container-based Cloud.
This project is under development at the moment. We encourage anyone who is interested in Shipyard to review our documentation.
If you find a bug, please feel free to create a Storyboard issue.