Split act-runner into its own pod and offer as a distinct stack. #612

telackey · 2023-10-27T01:03:25Z

telackey commented

2023-10-27 01:03:25 +00:00

This required a few fixes to allow for multiple pods in the same stack. Without the changes, the docker-compose.yml files would clobber each other.

$ laconic-so --stack act-runner deploy init --output act-runner.yml

$ laconic-so --stack act-runner deploy create --spec-file act-runner.yml --deployment-dir ~/opt/deployments/act-runner-1
$ echo "CERC_GITEA_RUNNER_REGISTRATION_TOKEN=FOO" >> ~/opt/deployments/act-runner-1/config.env
$ laconic-so deployment --dir ~/opt/deployments/act-runner-1 up

This required a few fixes to allow for multiple pods in the same stack. Without the changes, the docker-compose.yml files would clobber each other. ``` $ laconic-so --stack act-runner deploy init --output act-runner.yml $ laconic-so --stack act-runner deploy create --spec-file act-runner.yml --deployment-dir ~/opt/deployments/act-runner-1 $ echo "CERC_GITEA_RUNNER_REGISTRATION_TOKEN=FOO" >> ~/opt/deployments/act-runner-1/config.env $ laconic-so deployment --dir ~/opt/deployments/act-runner-1 up ```

dboreham approved these changes 2023-10-27 17:58:03 +00:00

Sign in to join this conversation.

No reviewers

No Milestone

No project

No Assignees

2 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cerc-io/stack-orchestrator#612