Hosting locally with Docker/Docker Compose?

[Lockszmith-GH]

Interesting project, Any tips on how to deploy it locally with docker?
I've never used CloudFlare's hosting / workers - I don't like putting my data on 'The Cloud' (aka someone's else's server) or 'Serverless' (aka, not on my server), so I'm wondering what are the components that are required to run this completley local.

I have a local Open WebUI instance that can act as a 'proxy' of sorts for any model I have registered there (local and remote/paid).
I can run PostgreSQL or MariaDB as needed, just trying to understand the setup.

If anyone has any experiece with this, I would appricate any input.

[Miko997]

I checked the repository because I was curious about this too. Docker deployment isn't officially supported yet.

The current production setup still depends on Cloudflare Workers, D1 and R2. There is an experimental local runtime using Bun, SQLite and local file storage, though:

bun install
bun run build:web

EDGE_EVER_AUTH_USERNAME=admin \
EDGE_EVER_AUTH_PASSWORD='your-password' \
EDGE_EVER_DATA_DIR="$PWD/.edgeever-data" \
bun run start:self-hosted

That should be enough for trying it locally. The intended Docker setup seems to be one application container with a persistent /data directory containing the SQLite database and attachments.

I wouldn't treat it as production-ready yet, though. There isn't an official Docker image, Compose file or documented backup/upgrade process. PostgreSQL is mentioned in the storage design, but it hasn't been implemented yet, and MariaDB isn't currently supported either.

The current status is explained here: [docs/self-hosting-architecture.md](https://github.com/tianma-if/edgeever/blob/main/docs/self-hosting-architecture.md).

So basically: local self-hosting is possible experimentally, but a supported Docker/Compose deployment is still on the roadmap.

[tianma-if]

Thanks for raising this — fully local self-hosting is a valid use case, especially for users who already operate a VPS, NAS, or home server and do not want to depend on Cloudflare.

The current status is:

• Cloudflare Workers + D1 + R2 remains the only officially supported production deployment.
• An experimental Bun runtime is already available and runs completely locally with SQLite plus a local attachment directory.
• The same runtime can optionally store attachments in an S3-compatible service such as MinIO, S3, OSS, COS, or R2.
• PostgreSQL is reserved in the storage contracts but is not implemented yet. MariaDB is not currently supported. Neither is required for the intended first Docker deployment; SQLite is the planned default.

You can try the experimental runtime with:

bun install
bun run build:web

EDGE_EVER_AUTH_USERNAME=admin \
EDGE_EVER_AUTH_PASSWORD="your-strong-password" \
EDGE_EVER_DATA_DIR="$PWD/.edgeever-data" \
bun run start:self-hosted

Then open http://localhost:8787.

One clarification regarding Open WebUI: EdgeEver does not currently call an LLM provider directly, so an OpenAI-compatible model proxy is not needed to run EdgeEver itself. EdgeEver exposes REST/OpenAPI and a remote MCP endpoint at /mcp. An AI client that supports the EdgeEver MCP endpoint can use whichever local or remote model you configure in that client. Whether Open WebUI can be connected directly depends on its MCP/tool integration.

Official Docker/Compose support still needs more than packaging the command above. Before calling it production-ready, we need a tested container image, persistent-volume permissions, database and attachment health checks, graceful shutdown, backup/restore and upgrade procedures, multi-architecture images, and deployment documentation. I will track that supported Docker/Compose deliverable separately from the experimental runtime work; there is no confirmed release date yet.

The current architecture and environment variables are documented here:
https://github.com/tianma-if/edgeever/blob/main/docs/self-hosting-architecture.md

Thanks again — this discussion is useful confirmation that a Cloudflare-independent deployment path matters to users.

[wxyShine]

建议增加自部署到自有服务器方案 比如 docker run 、 docker compose