Skip to content

Latest commit

 

History

History
59 lines (37 loc) · 1.59 KB

SPONSORSHIP.md

File metadata and controls

59 lines (37 loc) · 1.59 KB

Sponsorship

Being a sponsor of RunsOn gets you access to the following features:

  • Full access to the complete source code: server and agent. Especially useful if you want to control the entire supply chain, and/or are just curious.

  • Possibility to make changes to the source code, as long as it's kept for internal use.

  • Dedicated Slack Connect channel with the RunsOn author.

  • Faster email support.

More details about license types here.

Rebuilding the RunsOn docker image to host in your own registry

First installation

  1. Create a public ECR registry in your AWS account.

  2. Clone, cd into the RunsOn repo and fetch the private submodules:

git clone https://github.com/runs-on/runs-on
cd runs-on
git submodule update --init --recursive
  1. Create a .env.local file with the following variable:
REGISTRY=public.ecr.aws/your/repo/path
  1. Rebuild and push the docker image to your registry:
AWS_PROFILE=your-aws-profile-with-ecr-access make build-push
  1. Create the CloudFormation stack as per the official instructions, but make sure to use the new registry path as the value for the AppRegistry parameter.

Upgrading to a new RunsOn version

  1. Update the repo and submodules to the latest version:
cd runs-on
git pull
git submodule update --init --recursive
  1. Rebuild and push the docker image to your registry:
AWS_PROFILE=your-aws-profile-with-ecr-access make build-push
  1. Upgrade the CloudFormation stack as per the official instructions. The AppRegistry parameter should already be set.