Skip to content

AngeMedia Gateway v0.2.0

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 13 Jun 20:50
· 42 commits to main since this release
v0.2.0
aa21980

AngeMedia Gateway v0.2.0

This release establishes the first stable v0.2.0 foundation for AngeMedia Gateway: a self-hosted media generation gateway with a minimal Web Studio, safer provider handling, job/asset tracking, and Docker deployment support.

Highlights

  • New minimal Web Studio for login, dashboard, image generation, providers, jobs, assets, gateway API keys, and account management.
  • Single-admin account APIs and Web Studio account modal for username/password changes.
  • Username/password changes require the current password and invalidate existing sessions.
  • Gateway API Keys cannot access admin/account APIs.
  • Catalog-aware image generation UI with clearer default/catalog/custom provider model handling.
  • Provider catalog and built-in/reserved provider sections are read-only in v0.2.0 and configured through environment variables.
  • Pollinations is disabled by default and treated as experimental.
  • Image generation results are localized into protected assets.
  • Video generation supports submit/status flows; there is no background worker queue in v0.2.0.
  • Jobs and Assets provide a minimal usable tracking and browsing flow.
  • /generated/* and /uploads/* are protected and support authenticated HEAD.
  • Dockerfile, docker-compose example, and DockerHub publishing workflow added.

Docker

Images:

maxblack777/angemedia-gateway:v0.2.0
maxblack777/angemedia-gateway:latest

The latest tag is only published for stable version tags, not for main branch pushes.

Verified gates

  • Full CI test suite passed on Python 3.10, 3.11, and 3.12.
  • Web Studio JavaScript syntax check passed.
  • GitHub Actions CI passed.
  • Docker build and compose smoke passed.
  • DockerHub workflow passed for main/edge before release.
  • Remote staging previously passed real image/video E2E on the runtime commit; later commits were documentation and Docker packaging only.

Known limits

  • Python 3.13 is not part of the v0.2.0 supported CI matrix.
  • No Redis/Celery/K8s worker queue in v0.2.0.
  • No SaaS, multi-tenant, billing, team workspace, or hosted control plane.
  • No v0.1 data migration/backfill.
  • Built-in provider credentials are still environment-driven, not fully editable through the Web Studio.
  • Diagnostics, job event detail, provider fallback-chain UI, and richer provider management are planned for later versions.
Assets 4
Loading