Self-Hosted Introduction
Since Actionsflow v1.6.0, Actionsflow can be deployed as a self-hosted application. You can run Actionsflow by Docker or manually.
Getting started
Docker
# You can also clone your own repogit clone https://github.com/actionsflow/actionsflow-workflow-default.gitcd actionsflow-workflow-defaultdocker run -it -v /var/run/docker.sock:/var/run/docker.sock -v ${PWD}:/data -p 3000:3000 actionsflow/actionsflow
Notice: Actionsflow's dependency act need
/var/run/docker.sock
to run and manage the Github Actions.
Manual
Prerequisites
Run
# You can also clone your own repogit clone https://github.com/actionsflow/actionsflow-workflow-default.gitcd actionsflow-workflow-defaultnpm inpm start
The default webhook endpoint will be ran at http://localhost:3000/webhook/
Env
You can use .env
file to define the environment variables at your root directory. For example:
TEST=testCI=true
Note: you shouldn't commit this to your repo
Secrets
You can use .secrets
file to define the secrets variables at your root directory For example:
TOKEN=testPASSWORD=test1
Note: you shouldn't commit this to your repo