Seperate the runner and jobs to a network just for themselves.

Select the host in the deploy script, default to all hosts.

The issue I'm trying to address here is that because of the Docker
volume, /builds/foo is really /var/lib/docker/volumes/123/_data/foo.
This causes some interesting issues with addressing files with Docker
from inside a Docker container. Do it just on ns4 (for now, if it works
and needed I may do it on host01 too). Also, deploy to the kodi host
last because it has issues right now.

- Use CI templates.
- Use common pre-commit config from snippet.
- Address pre-commit issues.

Can't deploy with the runner, the jobs fail because the runner is
restarted during. Do the pull and build with the CI, but the actual
deployment with a script locally.

Can't use the "host" variable as the tag. Workaround that with YAML
anchors (ugly but works).

- New version.
- pre-commit.
- GitLab CI/CD.
- Always pull new images.

Needed for easier mounting using `--volumes-from` to acces the files
when running another container (launching a container from inside a
container, for an example see the CI from
https://git.shore.co.il/nimrod/resume).

Set the runners to run untagged jobs (I only enabled tagging to run
specific jobs in specific runners, the untagged jobs should still run
wherever).

Move the runner specific files to the `runner` directory.

Run the docker-clean image daily. Remove failed builds and such.

Tag with the runner name (useful for deployments so I don't have to copy
files over SSH).

On host01.shore.co.il or different hosts.

Otherwise this creates multiple runners in the same container.

Can be easily deployed on different hosts by setting different
environment variables (need to document them). No testing/ linting of
any kind (need to do that as well).