Feature Description
First off: this is great. OpenConcho is exactly the kind of UI that makes a self-hosted Honcho instance much easier to inspect and use.
It would be valuable if the web app were easier to package and run in Docker, so it can be added directly to a user's existing Honcho docker-compose stack.
Motivation
Honcho's recommended self-hosting path is Docker Compose. If OpenConcho had first-class Docker support, users could run the API, database, deriver, Redis, and web UI from the same Compose project instead of separately managing a Node/pnpm dev server or desktop app.
Proposed Solution
Consider adding one or more of:
- A production
Dockerfile for @openconcho/web
- A published container image for the web app
- A
docker-compose.yml or documented Compose snippet that can be dropped into a Honcho stack
- An nginx/static-server config that proxies Honcho API paths like
/v3/* and /health to the Honcho API service, allowing the web app to use same-origin requests and avoid browser CORS issues
- A configurable default Honcho base URL for Docker deployments
Example shape:
openconcho:
image: ghcr.io/offendingcommit/openconcho-web:latest
depends_on:
api:
condition: service_healthy
ports:
- "127.0.0.1:5173:80"
restart: unless-stoppedAlternatives Considered
The current web dev flow works well for development, and the desktop app is useful, but a Docker-packaged web app would better match the common self-hosted Honcho deployment model.
Note: this issue was dictated, not read.
Feature Description
First off: this is great. OpenConcho is exactly the kind of UI that makes a self-hosted Honcho instance much easier to inspect and use.
It would be valuable if the web app were easier to package and run in Docker, so it can be added directly to a user's existing Honcho
docker-composestack.Motivation
Honcho's recommended self-hosting path is Docker Compose. If OpenConcho had first-class Docker support, users could run the API, database, deriver, Redis, and web UI from the same Compose project instead of separately managing a Node/pnpm dev server or desktop app.
Proposed Solution
Consider adding one or more of:
Dockerfilefor@openconcho/webdocker-compose.ymlor documented Compose snippet that can be dropped into a Honcho stack/v3/*and/healthto the Honcho API service, allowing the web app to use same-origin requests and avoid browser CORS issuesExample shape:
Alternatives Considered
The current web dev flow works well for development, and the desktop app is useful, but a Docker-packaged web app would better match the common self-hosted Honcho deployment model.
Note: this issue was dictated, not read.