Skip to content

v0.2.0: Docker setup and richer file review

Latest
Latest

Choose a tag to compare

View all tags
@bhatiadheeraj bhatiadheeraj released this 21 Oct 01:46
· 8 commits to main since this release
v0.2.0
c850137

Reloops OSS v0.2.0 improves local installation and file review, with automated coverage for uploads, sharing, and Docker persistence.

Install and upgrade

From a checkout of this release:

docker compose up -d --build --wait --wait-timeout 600

Open http://127.0.0.1:6173. Docker now serves the production web build, runs the local backend and metadata worker, and retains database and uploaded files across normal restarts. Startup applies pending migrations and stops on migration errors without resetting existing data. The repository's backend files and Docker socket are required; this release builds reloops-oss:local locally.

For an existing checkout, keep your .env, back up your database and uploads, pull the release, and rebuild. See Local Setup for configuration and shutdown instructions.

File review

  • PDFs receive browser-generated first-page thumbnails for both member and guest uploads.
  • Upload progress and drag overlays match the cloud UI; canceling during thumbnail creation no longer finalizes an upload.
  • Shared asset and collection reviews show existing comments, annotation drawings, and member display names. Older annotation field formats remain readable.
  • Audio files have playback controls and decoded waveforms in member and project-share reviews.
  • Shared collection headers include the creator's public name and avatar.

Reliability and tests

  • Added unit coverage, browser tests for PDF rendering and audio playback, backend sharing/permission checks, and Docker restart/persistence integration tests.
  • Added GitHub Actions workflows for web, backend, and Docker validation.
  • Docker startup waits for project-sharing readiness before exposing the web app.
  • Local demo recordings, installed demo tooling, credentials, and generated reports stay outside Git.

Metadata configuration

The default metadata provider is mock: it generates placeholder metadata from file properties, without inspecting file contents. Provider configuration and requeue instructions are documented in the setup and worker guides.

Full changelog: v0.1.0...v0.2.0

Release validation: Web and fresh-backend CI and Docker build, runtime, and restart integration CI passed for this release.

Assets 2
Loading