neale/big-builder
neale
/
big-builder
1
0
Fork 0
Code Issues 1 Pull Requests Packages Projects Releases Wiki Activity

easier setup instructions

This commit is contained in:
Neale Pickett 2023-10-27 23:14:38 -06:00
parent a5defa3349
commit 92c387da4f
1 changed files with 12 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
README.md
View File

@ -19,22 +19,23 @@ so I'm able to do everything I want that way.
How To Set This Up How To Set This Up
------------------ ------------------
This wants its files to live in `/app`. 1. Go get a runner registration token from your forgejo/gitea instance.
After you do the registration step, 2. Decide in advance what tags you want to use.
that can be mounted read-only. `big-builder,go,python3,hugo` isn't an awful choice.
But it will want to write its token in the registration step. 3. Run this:
```sh
mkdir /srv/big-builder
docker run --rm -it -v /srv/big-builder:/app big-builder # This will ask you 3 questions
docker run -d --restart=always -v /srv/big-builder:/app:ro big-builder daemon
```
You should provide custom tags:
that's how you keep it from trying to use docker.
On my raspberry pi, On my raspberry pi,
I used `["big-builder", "aarch64", "go", "python3", "hugo"]`. I used the tags `aarch64,big-builder,go,python3,hugo`.
Otherwise, just set this up the same way you would set up the More documentation is at
[gitea act runner](https://docs.gitea.com/usage/actions/act-runner). [gitea act runner](https://docs.gitea.com/usage/actions/act-runner).
To run in daemon mode,
you have to give it `daemon` on the commandline:
I didn't make a fancypants script to guess the command.
Adding Other Packages Adding Other Packages