dotya.ml/drone-ci-configs
2
0
Fork 0
Code Issues Pull Requests Releases Activity
🤖 drone.dotya.ml configuration files https://drone.dotya.ml
6 Commits 1 Branch 0 Tags 77 KiB
Shell 50%
Dotenv 50%
2c3835d445
Go to file
surtur 2c3835d445
manage system access of the service using systemd 
* add drone.slice (control resource usage)
* restrict can be accessed by the service
* adjust IO priority and NICEness of processes created withing the
  service
* use "-p" with docker-compose invocation to specify a project that the
  newly-spawned containers belong to (best practice)
* add commented override
2022-03-20 20:54:52 +01:00
.gitignore feat: added .gitignore 2020-05-29 12:56:12 +02:00
docker-compose.yml feat: as a precaution, have some runner dirs under tmpfs 2020-05-30 11:10:30 +02:00
drone.service manage system access of the service using systemd 2022-03-20 20:54:52 +01:00
drone.slice manage system access of the service using systemd 2022-03-20 20:54:52 +01:00
README.md initial commit 2020-05-29 12:52:54 +02:00
runner-docker.env feat: added docker-compose.yml + env files 2020-05-29 12:57:21 +02:00
server.env feat: added docker-compose.yml + env files 2020-05-29 12:57:21 +02:00

README.md

drone.dotya.ml

this repo holds

  • docker-compose.yml for drone instance
  • drone-related env files
  • systemd Unit file to easily start/stop the instance as a service

prepare environment

mkdir -pv /etc/drone

  • put docker-compose.yml + env files in there

  • put drone.service systemd unit file in /etc/systemd/system/drone.service

  • reload systemd daemon

systemctl daemon-reload

enable running drone "service" after system startup and start drone now

systemctl enable --now drone.service

notes

  • in current set-up you also need a web proxy server (such as nginx) to forward traffic to and from drone that runs exclusively on localhost
  • this set-up works with Gitea in mind, although it shouldn't be too hard to change the configs to work with other git providers