dotya.ml/ drone-ci-configs
2
0
Fork 0
Code Issues Pull Requests Releases Activity

update README.md

This commit is contained in:
surtur 2022-03-26 03:11:11 +01:00
parent 38e53c1060
commit 358a77d168
Signed by: wanderer
GPG Key ID: 19CE1EC1D9E0486D
1 changed files with 25 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

45
README.md
View File

@ -1,32 +1,37 @@
# drone.dotya.ml # [drone-ci-configs](https://git.dotya.ml/dotya.ml/drone-ci-configs)
this repo holds this repo holds
* docker-compose.yml for [drone](https://drone.io) instance * `docker-compose.yml` for [drone.dotya.ml instance](https://drone.dotya.ml) of
* drone-related env files [Drone CI](https://drone.io)
* `systemd` Unit file to easily start/stop the instance as a service * drone-related env files (`server.env`, `runner-docker.env`)
* `systemd` *Unit* file to easily start/stop the instance service and `systemd`
*Slice* file to control its resource usage
#### prepare environment ### prepare environment
```bash ```bash
mkdir -pv /etc/drone mkdir -pv /etc/drone /etc/systemd/system/drone.service.d
``` ```
* put `docker-compose.yml` + env files in there * unless running with unprivileged user, copy `drone.service` and `drone.slice`
files to `/etc/systemd/system` and `override.conf` into
* put `drone.service` `systemd` unit file in `/etc/systemd/system/drone.service` `/etc/systemd/system/drone.service.d`
* reload `systemd` daemon * reload `systemd` daemon
```bash
systemctl daemon-reload
```
```bash * let `drone.service` start automatically on system startup and start the
systemctl daemon-reload service immediately
``` ```bash
systemctl enable --now drone.service
```
enable running `drone` "service" after system startup and start `drone` now alternatively, copy the folder structure `etc` to your `/etc`
```bash ### notes
systemctl enable --now drone.service
```
#### notes * using this set-up a reverse proxy (such as `nginx`) is also needed to forward
traffic to and from `drone` server that listens exclusively on localhost
* 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
* 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 change the configs to work with other git providers (see `server.env` file)