Sign inSign up

mreza0100/appflowy-cloud-agpl

By mreza0100

•Updated about 2 months ago

AppFlowy Cloud self-hosted, built from AGPL source: no 1-user seat limit, unlimited members

Image
Developer tools
Content management system
0

139

mreza0100/appflowy-cloud-agpl repository overview

⁠AppFlowy Cloud AGPL community build without the self-hosted one-user cap

This image is an unofficial community build of the AppFlowy Cloud API from the upstream AGPL source, which does not contain the distributed self-hosted image's one-user seat enforcement.

⁠Quick start

docker pull mreza0100/appflowy-cloud-agpl:latest

Pin a tag rather than tracking latest for anything you depend on: 581f123 is the upstream source commit this image was built from.

⁠The problem

The official prebuilt self-hosted API image can log the following messages and prevent a second member from joining a workspace:

Free plan limits - max_users: 1, max_guests: 3
No license data found for host
Seat limit reached: counted 1 Member/Owner users across initialized workspaces (limit 1).
Upgrade your license to add more seats.

The image in this repository is intended as a source-built replacement for the appflowy_cloud API container in that situation.

⁠Why it happens

AppFlowy's public README states that its distributed build is a closed-source fork of the public AppFlowy Cloud code combined with proprietary code. The public AGPL source at commit 581f123d48008dd4453be85a5133c554e34a51cb does not contain the self-hosted license or seat-limit implementation. This image builds that upstream source without source patches.

⁠Usage

Add this service override to an existing AppFlowy self-hosted Compose project, then recreate the API service. Keep the existing environment, dependencies, networks, health check, and hardening settings from the base Compose file.

services:
  appflowy_cloud:
    image: mreza0100/appflowy-cloud-agpl:581f123
docker compose pull appflowy_cloud
docker compose up -d --no-deps --force-recreate appflowy_cloud

Before changing an existing deployment, back up PostgreSQL and confirm schema compatibility. The published image is the API service, not a complete AppFlowy stack.

⁠Reproduce the source build

git clone https://github.com/AppFlowy-IO/AppFlowy-Cloud.git
cd AppFlowy-Cloud
git checkout 581f123d48008dd4453be85a5133c554e34a51cb
test -z "$(git status --short)"
DOCKER_BUILDKIT=1 docker build \
  --label org.opencontainers.image.source=https://github.com/AppFlowy-IO/AppFlowy-Cloud \
  --label org.opencontainers.image.revision=581f123d48008dd4453be85a5133c554e34a51cb \
  --label org.opencontainers.image.licenses=AGPL-3.0 \
  --label 'org.opencontainers.image.description=Unofficial community build of AppFlowy-Cloud from unmodified upstream AGPL source. Not affiliated with or endorsed by AppFlowy Inc.' \
  --tag appflowy-cloud-agpl:581f123 \
  .

The deployment build recipe uses BuildKit cache mounts but compiles the same unmodified source. No patches are applied to the upstream source. A copy of the upstream AGPL license is included in the published image at /usr/share/licenses/appflowy-cloud-agpl/LICENSE.

The corresponding source is available from the AppFlowy-IO/AppFlowy-Cloud repository⁠, under the GNU Affero General Public License v3.0.

⁠What this is not

This is unofficial software, is not affiliated with or endorsed by AppFlowy Inc., and is provided without warranty. AppFlowy is a trademark of AppFlowy Inc. This image does not include PostgreSQL, Redis, object storage, authentication, a reverse proxy, or a web client; those services must be deployed and configured separately.

Tag summary

Content type

Image

Digest

sha256:ff369afb0…

Size

52.2 MB

Last updated

about 2 months ago

docker pull mreza0100/appflowy-cloud-agpl