Deal with a non Kiwix organisation

[kelson42]

Assuming someone wants to benefit from our CI/CD but already owns the app in his organisation:

• How could we upload a custom app to his organisation instead of ours?
• What kind of things should be changed?

[BPerlakiH]

Some initial thoughts on this:

In the first run I think the best would be to have a developer access to the AppStore of the first client, to actually see if things appearing on the other end of the CD process.

Here are the moving parts we need to "inject":

• APPLE_DEVELOPMENT_SIGNING_CERTIFICATE
• APPLE_DEVELOPMENT_SIGNING_P12_PASSWORD
• SIGNING_CERTIFICATE
• SIGNING_CERTIFICATE_P12_PASSWORD
• App Name
• App version
• Build number (in case of combined iOS / macOS releases, it's better to update the increasing build number)
• The naming of the output files also requires some edits, as we have Kiwix-$Version prefix there.

In increased number of such clients, we need to have a look how we want to manage the secret keys, eg. with some prefixing: APPLE_${CLIENT}DEVELOPMENT...

Once we have 1 running, for additional clients we might automate this process further.

Additional nice to have goals: to have the release notes / screenshots automated.

[kelson42]

@BPerlakiH Thank you for your feedback. All of this should be customisable either in the json or in the secrets.

[kelson42]

We should probably use the concept of GitHub environnement