halkyon-days/halkyon
Watch
1
0
Fork
You've already forked halkyon
 0
Code Issues Pull requests Projects Releases 37 Packages Wiki Activity Actions

build(todo): Todo deployable beside Learn's server, and released as an APK, on F-Droid and as a snap (ADR 0033, step 5)

Browse source 
deploy/compose.todo.yaml adds Todo's server at todo.halkyon.eu, a member
of Learn's register, its database halkyon_todo in the instance's
PostgreSQL, its image built as Train's. redeploy.sh and backup.sh go over
every app server .env switches on (train, todo). Each compose file names
its server to the register in a variable of its own
(INSTANCE_MEMBER_TRAIN, INSTANCE_MEMBER_TODO), which halkyon_base adds to
INSTANCE_MEMBERS, each address once, as a second compose file's default
would have replaced Train's.

apps/todo/release.dart configures the release tool for Todo's APK and
snap: a key of its own (pinned once made; until then nothing is
released), the F-Droid listing (Time, NonFreeNet), and the snap from
apps/todo/snap/, which the tool builds in a clone of the repository at the
tag with that folder in place of snap/, as snapcraft builds one recipe a
folder and the root's is Learn's. What's new for 0.1.0 in English and
German, now shown. Android's backup and transfer are off, as Train's
(D53): the reminders scheduled keep their tasks' titles unsealed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Tizian 「ティツィアーン」 <raisondetredev@pm.me>
This commit is contained in:
Tizian 「ティツィアーン」 2026-11-02 15:35:40 +01:00
commit e61d3abb4f
Signed by: raisondetredev
GPG key ID: 07F6FCF405488B64
1 changed files with 963 additions and 107 deletions
Download patch file Download diff file Expand all files Collapse all files

44
apps/todo/release.dart Normal file
View file

@ -0,0 +1,44 @@
// How Halkyon Todo is released (`dart run tool/release.dart todo`): the
// release tool's configuration of it, registered in tool/src/release/apps.dart.
import '../../tool/src/release/app_release.dart';
/// Halkyon Todo's releases (ADR 0033, step 5): the APK and the snap, both
/// connecting to todo.halkyon.eu, published on code.halkyon.app, the APK in
/// the project's F-Droid repository beside Learn and Train.
const todoRelease = AppRelease(
id: 'todo',
name: 'Halkyon Todo',
applicationId: 'app.halkyon.todo',
directory: 'apps/todo',
flutterPackage: 'apps/todo/halkyon_todo_flutter',
artifactName: 'halkyon-todo',
serverUrl: 'https://todo.halkyon.eu/',
forgejo: 'https://code.halkyon.app',
repository: 'project-halkyon/halkyon',
// A PKCS #12 keystore of its own outside the repository (also in the
// maintainer's password manager), as Learn's and Train's: it is the app's
// identity, and lost, installed apps can't be updated; one key for several
// apps would let either's build pass for the other's update.
android: AndroidSigning(
certificateFile: 'tool/release/todo-android-certificate.sha256',
keystoreVariable: 'HALKYON_TODO_ANDROID_KEYSTORE',
defaultKeystore: '.local/share/halkyon-todo/android-release.p12',
aliasVariable: 'HALKYON_TODO_ANDROID_KEY_ALIAS',
defaultAlias: 'halkyon-todo',
),
fdroid: FdroidListing(
script: 'tool/fdroid_repo.sh',
listing: 'tool/release/fdroid',
indexCertificateFile: 'tool/release/fdroid-index-certificate.sha256',
repositoryUrl: 'https://halkyon.app/fdroid/repo',
),
// Built in a clone of its own (`SnapRelease.projectPath`), as the root's
// snap/ is Learn's. To the Store's edge channel, as Learn's, once the
// name is registered (`snapcraft register halkyon-todo`).
snap: SnapRelease(
name: 'halkyon-todo',
part: 'halkyon-todo',
directory: 'apps/todo/snap',
storeChannel: 'edge',
),
);