Drone

(2 intermediate revisions by the same user not shown)

Line 8:

Dockerfiles to build an Alpine-based image can be found [https://github.com/drone/drone/tree/master/docker here].

==Crypto==

By default, drone will be using <tt>/etc/certs/drone.company.com/server.crt</tt> and <tt>DRONE_TLS_KEY=/etc/certs/drone.company.com/server.key</tt>.

==Datastore==

Drone keeps its data in <tt>/data</tt> within the Docker container, presumably backed by some persistent file outside. This primarily consists of a single large SQLite file (mine ran just about 2GB after 5,000 builds).

===build_trigger===

Drone claims to cut off after 5,000 builds, but my database showed 5,037. Sorting by <tt>build_trigger</tt>, I counted 19 with "dankamongmen", and 18 with no data in this field. Clearing the column in all builds did not bypass the license, however. At that point, I used the splendid [https://sqlitebrowser.org/ SQLitebrowser] to remove the earliest 1,000 builds. Drone now started up without licensing problems.

Better would be to build the OSS binary and copy it into the container, now that I'm pretty sure they use the same schema etc. A naive attempt to do this resulted in drone failing to start with some manner of <tt>ENOENT</tt>.

==See also==

* "[https://blog.almeroth.com/ Build & Run: Drone (Open Source Edition)]" by Jon Almeroth, 2020-05-12

Drone: Difference between revisions

Dank (talk | contribs)

@@ Line 8: / Line 8: @@
 Dockerfiles to build an Alpine-based image can be found [https://github.com/drone/drone/tree/master/docker here].
+==Crypto==
+By default, drone will be using <tt>/etc/certs/drone.company.com/server.crt</tt> and <tt>DRONE_TLS_KEY=/etc/certs/drone.company.com/server.key</tt>.
+==Datastore==
+Drone keeps its data in <tt>/data</tt> within the Docker container, presumably backed by some persistent file outside. This primarily consists of a single large SQLite file (mine ran just about 2GB after 5,000 builds).
+===build_trigger===
+Drone claims to cut off after 5,000 builds, but my database showed 5,037. Sorting by <tt>build_trigger</tt>, I counted 19 with "dankamongmen", and 18 with no data in this field. Clearing the column in all builds did not bypass the license, however. At that point, I used the splendid [https://sqlitebrowser.org/ SQLitebrowser] to remove the earliest 1,000 builds. Drone now started up without licensing problems.
+Better would be to build the OSS binary and copy it into the container, now that I'm pretty sure they use the same schema etc. A naive attempt to do this resulted in drone failing to start with some manner of <tt>ENOENT</tt>.
 ==See also==
 * "[https://blog.almeroth.com/ Build & Run: Drone (Open Source Edition)]" by Jon Almeroth, 2020-05-12