From cdce868b3f1decb8bddd34c7a550522f4454d13c Mon Sep 17 00:00:00 2001 From: L3D Date: Fri, 12 May 2023 15:32:03 +0200 Subject: [PATCH] Explain mechanism --- README.md | 18 +++++++++++++++--- 1 file changed, 15 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index aec6e98..0ed2d42 100644 --- a/README.md +++ b/README.md @@ -1,7 +1,14 @@ # kivy - My first App ...to test and setup a build pipeline -## Setup +Obviously we use [kivy](https://kivy.org/) for this 'Hello World'. The app itself does nothing except displaying the words "Hello World!". +But the exciting part of this git repo is the build pipeline + +Since a fe weeks forgejo/gitea have implemented github actions. And we use them to build the app. + +## Setup local Development +For local app development, be inspired by this setup: + Venv and Requirements ``` python3 -m venv app @@ -18,5 +25,10 @@ python3.11 setup.py build_ext --inplace make install ``` -## Note -This is work in progress! +## Build Pipeline +### Bulldozer building +There is a Github Action for building kivy apps for android using bulldozer. We mirrored the app to [https://backwesen.de/actions/gh-buildozer-action](https://backwesen.de/actions/gh-buildozer-action.git) and use it successfully for building our app. + +### Releasing +Sadly gitea/forgejo does not support artifacts jet. So we have multiple different options for releasing our build binarys. Publishing them to other servers, put them in a new git repo or maybe there is a fancy way to attatch them to a release. For now we skipped this option and waiting for artifacts to become available. +In the meantime we use https://transfer.sh/ for uploading our files quick and dirty.