don't push the stable link anymore; linking git crypt guide

This commit is contained in:
missytake
2019-12-06 11:01:41 +01:00
parent a569694b4d
commit ee1405ce87
+3 -3
View File
@@ -21,12 +21,12 @@ Release core, f-droid, then:
3. Select flavor `gplayRelease` with V1 signature enabled
(needed for easy APK verification), V2 is optional
4. Upload the generated APK from `gplay/release` to download.delta.chat.
You need the private SSH key of the jekyll user; you can find it in the git-crypt secrets of the otf repo.
You need the private SSH key of the jekyll user; you can find it in this file: https://github.com/hpk42/otf-deltachat/blob/master/secrets/delta.chat
It is protected with [git-crypt](https://www.agwa.name/projects/git-crypt/) - after installing it, you can decrypt it with `git crypt unlock`.
If your key isn't added to the secrets, you can ask missytake@systemli.org to add you.
Add the key to your `~/.ssh/config` for the host, or to your ssh-agent, so rsync is able to use it.
- `cd gplay/release`
- `rsync deltachat-gplay-release-0.*.apk jekyll@download.delta.chat:/var/www/html/download/android/`
- `ln -s deltachat-gplay-release-0.*.apk deltachat-stable.apk`
- `rsync -l deltachat-stable.apk jekyll@download.delta.chat:/var/www/html/download/android/`
5. Test the APK
6. Upload the APK as _Beta_ (_not:_ Production) to https://play.google.com/apps/publish/
(Release management/App releases/Open track/Manage/Create Release/Browse files ->