Install and build Condui Community

Install the local Community edition with Docker Compose or Podman, or build and start it directly from source.

Condui Community is the self-hosted, local edition of Condui. It works without an account, database, or managed Condui service. You can build the source yourself and run the application on your own computer or server.

The Community edition stores projects in the browser on the device where you work. Downloaded Condui project archives are compatible in both directions with the hosted edition.

View the Condui Community source on GitHub.

Which installation method should you use?

The supplied Dockerfile builds a standard OCI container image. Other OCI-compatible container tools can also build the image, but Docker and Podman are the tested routes.

Requirements

For Docker Compose or Podman, you need:

• Git, or a downloaded copy of the repository;
• Docker with the Compose plugin, or a recent Podman installation;
• a free local port, 8080 by default; and
• a modern browser.

A direct source build requires Node.js 24 and npm. You do not need a Supabase project, cloud account, or separate database.

Install with Docker Compose

1. Fetch the repository and open its directory:

git clone https://github.com/Xoliul/condui-community.git
cd condui-community

1. Build and start the container:

docker compose up --build -d

1. Open http://localhost:8080. The Condui Community home page appears when the container is ready.

1. Check the status or logs if needed:

docker compose ps
docker compose logs -f

Stop the application with:

docker compose down

Install with Podman

Build the OCI image:

podman build -t condui-community:local .

Then start the container:

podman run --name condui-community --rm -p 8080:8080 condui-community:local

Open http://localhost:8080. Press Ctrl+C to stop the container. You can also use the supplied compose.yaml with Podman Compose.

Build and start from source

First confirm that Node.js 24 is active:

node --version

Install the locked dependencies, build the production application, and start the local server:

npm ci --ignore-scripts
npm run build
npm start

Then open http://localhost:8080. The local server provides both the web application and the local conversion endpoints for supported plan files.

Update the installation

Fetch a newer Community snapshot and rebuild the container:

git pull
docker compose up --build -d

Download project archives for important projects before updating. Supported archives are migrated when opened, but your own backup remains the safest recovery option.

Project storage and backups

Projects are stored in the browser, not in the container. Replacing or rebuilding the container does not normally remove that browser storage. However, the browser treats each combination of protocol, hostname, and port as a separate origin. Moving from localhost:8080 to another hostname or port can therefore show an empty project list.

Regularly download important projects as Condui project archives and keep them in a backed-up location. A PDF is an output document and does not contain an embedded editable project in the Community edition.

No managed backup or support

A Community installation has no managed cloud storage, recovery service, or official support guarantee. The person operating it is responsible for updates, availability, and backups.

Common problems

• Port 8080 is already in use: change 8080:8080 in compose.yaml to, for example, 8081:8080, then open http://localhost:8081.
• The source build refuses to start: check that node --version reports version 24.
• The project list appears empty: open the application with exactly the same hostname and port, or import a previously downloaded project archive.
• The container stops while building: inspect docker compose logs and check that Docker has enough memory and free disk space.