Today. No Linux target in electron-builder.yml, and no app-electron/bin/linux-x64/ binaries.
Wanted. AppImage and/or deb, plus NVENC-capable ffmpeg builds for the platform.
The known caveat. safeStorage.isEncryptionAvailable() is false on a desktop with no keyring (or a headless session), and buildCipher() in app-electron/src/main.ts deliberately returns undefined rather than a cipher that quietly stores plaintext. The API then keeps S3 credentials in memory only and logs it once — so on such a system every session is stranded by a restart, which surfaces as "Credentials unavailable after restart — create the session again from the CMS". That fallback works and is honest; a Linux release should decide whether it is acceptable, or whether to prompt the user to set up a keyring (gnome-keyring / kwallet) as part of onboarding.
Migrated from Todo.md item 3, which is removed as the repository is prepared to go public.
Today. No Linux target in
electron-builder.yml, and noapp-electron/bin/linux-x64/binaries.Wanted. AppImage and/or deb, plus NVENC-capable ffmpeg builds for the platform.
The known caveat.
safeStorage.isEncryptionAvailable()is false on a desktop with no keyring (or a headless session), andbuildCipher()inapp-electron/src/main.tsdeliberately returnsundefinedrather than a cipher that quietly stores plaintext. The API then keeps S3 credentials in memory only and logs it once — so on such a system every session is stranded by a restart, which surfaces as "Credentials unavailable after restart — create the session again from the CMS". That fallback works and is honest; a Linux release should decide whether it is acceptable, or whether to prompt the user to set up a keyring (gnome-keyring/kwallet) as part of onboarding.Migrated from
Todo.mditem 3, which is removed as the repository is prepared to go public.