This repo contains code for Runway, a software system for integrating data to Ed-Fi. It can be deployed locally via Docker or in AWS.
Runway is a friendly UI over our open source tools Earthmover and Lightbeam for loading flat files (particularly assessments) to an Ed-Fi ODS. But note that Runway itself is not open source, but non-commercial. It is free to use for Education Agencies and non-profits, but requires a license for for-profit entities. See our license for details.
The system consists of several components:
- the Application frontent and backend (see
app/), with which users interact to set up Ed-Fi connections and run integration jobs - the Executor (see
executor/), which executes Jobs, transforming input data and sending it to an Ed-Fi API
The Executor uses earthmover to transform input data and lightbeamto send it to an Ed-Fi API.
You can deploy this app in AWS or locally. Once deployed, see application features for tips on how to use the app.
Prerequisites:
- You must have an AWS account
- You must have deployed a custom VPC, 2 public subnets, and 2 private subnets before deploying the Runway templates. It is not advisable for users to use the default VPC initially deployed by AWS.
- You must have created a Hosted Zone and NS record for the domain at which you intend to deploy your Runway environment(s).
- You must have created a GitHub Connection in AWS CodePipeline between your GitHub and AWS accounts.
If you would like more guidance and support with deploying Runway in AWS, please reach out to our team using this form.
AWS Console Deployment Steps:
- In your AWS account, navigate to S3 and create an S3 bucket with a unique name that will be used to hold the Runway CloudFormation templates. Example bucket name:
{OrgName}-{ProductName}-{EnvironmentType}-cloudformationeducationanalytics-runway-dev-cloudformation
- Fork the Runway repository under your own Github account and use the
mainbranch. - Upload the contents inside of the cloudformation folder into your S3 bucket. Make sure the S3 bucket contains both
lambdasandtemplatesfolders with their respective files inside. - Copy the S3 URL for the
templates > 1-main.ymlfile. - Navigate to the CloudFormation console in AWS. Create a new stack with new resources.
- Select
Choose an existing template > Amazon S3 URLand paste your copied URL for the1-main.ymlfile into the field. ClickNext. - Enter stack parameter values. Please read the doc here for more information on parameter values and descriptions.
- Navigate through the next screens on the console until you are able to start the deployment.
Build the Executor Docker image with
cd executor && docker build -t runway_executor . && cd ..docker-compose.yml stands up containers including:
- a Postgres database which backs the application
- the App frontend and backend
- a Job Executor
Start up the stack with
docker-compose -f ./docker-compose.yml --env-file .\.env up -d(For an end-to-end working example, you may also want an Ed-Fi API running in another Docker stack. You'll also need to modify the Ed-Fi API's credentials to allow writing to the namespace uri://www.nwea.org.)
Go to localhost:3000 to view the job that's automatically launched when the stack starts. After about 15 seconds, the sample job will begin executing and you should see the status update.
Shut down a running stack with
docker-compose -f ./docker-compose.yml --env-file .\.env down --volumesThe entrypoint for the job_executor is init.sh, which calls a "prepare" bash script followed by an "execute" Python script. (Some setup steps are easier to write in bash, others in Python; hence the split.)
Coming soon...
This repo also contains a folder bundleSchemas/ which contains several examples of JSON schemas (which a bundle could provide) that would be turned into form elements on the "create job" part of this app, to collect configuration settings to be passed into the bundle.
Such schemas can be turned into form elements using (for React) react-jsonschema-form or (for jQuery) jsonform, jsonToForm, or json-editor.