v0.0.1-alpha.11
Pre-releaseFeatures
- Ring somebody into the call from the call controls
- Add somebody to a call from inside the call
- A Calls & data screen, and a phone that reports what it moved
- A Calls & Data page, and per-link measurement to fill it
- Record what each link in a call moved, and add up a month of them
Bug fixes
- Size the surface to the frame, so "fit" actually fits
- Show a whole camera, and give the call dock room to breathe
- Drop an answer that arrives after the connection is already settled
Other changes
- Changes done for new release
- Note why the scaling type alone did not stop the crop
- Record the in-call ring on the web, and the phone showing a whole frame
- Record the per-link call data, the analytics page and the Android screens
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.11-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.11.
Images
aiyuayaan/betweenus:<service>-0.0.1-alpha.11, 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.