v0.0.1-alpha.6
Pre-releaseFeatures
- A platform a release skips keeps the last one's artifacts
- A marker can name the platforms it is for
- Reconnect a dropped call, and end one that cannot be reconnected
- A notification read on one device takes itself down on the others
- The connection panel, ported from the desktop
- The green speaking ring lights for your own tile too
- Do not wake a phone for a message being read on another device
- A daily update check, and an install that reports what happened
- The auto update screen, and the prompt on launch
- Fetch, download and hand over a newer release
- The rules for which release a device should install
Bug fixes
- The self-view snaps to a corner, and the chrome gets out of the way
- Video has the rounded corners it appears to have
- Every attachment goes out under the foreground service
Other changes
- Done with the enhancement
- The call-screen pass recorded in TRACK.md
- RELEASING.md, and the pass recorded in TRACK.md
- Remove outdated Android chat notification suppression and PiP design documents
- Catch every doc up to push suppression, self-update, and the send-path fix
- One send path for every attachment
- The daily check and the installer session
- Record the self-update phase
Artifacts
| Platform | This release |
|---|---|
| Server images | Built here |
| Desktop (Windows) | Built here |
| Android | Built here |
Install
Not every release rebuilds every platform. The Artifacts table
above says which of these were built here and which are the last
release's, re-attached unchanged - a download whose file name
carries an older version is that, and it is the current build for
its platform.
Desktop (Windows) — BetweenUs-0.0.1-alpha.6-Setup.exe
installs; -Portable.exe needs nothing.
Android — take the APK matching your device (arm64-v8a unless it is
old or an emulator), or universal if you would rather not choose. The
.aab is for Play, not for sideloading.
Server — docker-compose.yml, nginx.conf and backup.sh below are a
deployment folder. Put them beside your existing .env and:
docker compose --env-file .env pull
docker compose --env-file .env up -dSame project name, same volumes, same .env as a built deployment, so an
existing server keeps its database and its uploads. BETWEENUS_VERSION in
.env overrides the pinned version; unset, this bundle stays on
0.0.1-alpha.6.
Images
aiyuayaan/betweenus:<service>-0.0.1-alpha.6, built for
linux/amd64 and linux/arm64 under one tag - a 64-bit Pi, an Ampere VPS or an
Apple silicon Mac pulls the same name and gets its own architecture. The moving
tags <service>-alpha and <service>-latest are
pointed at it as the last step of the run.