Sources and dependencies
The program version, download location, file checksums and required libraries make environment preparation reproducible.
Recipes
Tested instructions.
Knowledge you can reuse.
A recipe describes where to get sources, which dependencies to prepare and how to build and test a program. Parameters for a particular phone are selected separately.
Catalogue
Recipes and tested combinations.
The registry list: package, version, recipe format, declared options and test results. A result refers to one combination: the optimization level, the processor and the options the program was built with and checked on the phone.
The catalogue will be fetched from the server.
Combination = optimization level · processor · options (+option enabled, -option disabled). “Works” means the probes passed on the phone for that combination. Changing options, the processor or the level is not a new recipe revision — it is another result of the same recipe.
The essentials
From source to a result on Android.
Building
Instructions cover configuration, compilation and any changes needed for Android. A successful build is separate from a runtime test.
Testing and results
A log, target device and execution result help establish what was actually checked.
Registry status
Results matter.
The registry distinguishes recipes that compile (builds), work (works) or need repair (broken), among other states. Recorded tests help assess a recipe.
The catalogue above shows recorded results for specific combinations; the complete Germux 2.0 installation workflow is being developed as a next step.
Publishing a shared recipe
A recipe should be reusable and identify its limits. AI can help prepare and check a change; publication is agreed with the user.
See library data →Admin
Recipe admin panel.
Visible after signing in as an administrator. Decisions are also checked by the Worker and account token.
Admin panel is waiting for an administrator session.