Docs: fix self hosting local deploy protocol (#433)
* fix: skip Docker check in ensure-postgres.sh when remote DATABASE_URL is set When DATABASE_URL points to a non-localhost host, the script now skips all Docker operations and only verifies remote DB connectivity via pg_isready directly. * fix: honor DATABASE_URL for remote postgres preflight * fix(make): clarify stop output for remote database * docs: add local deployment protocol guidance to SELF_HOSTING.md Clarify that local deployments without TLS should use http:// and ws:// instead of https:// and wss://. --------- Co-authored-by: Junlong Liu <junlong.liu@shopee.com>
This commit is contained in:
parent
d450b3d454
commit
0263ecce9e
3 changed files with 91 additions and 16 deletions
|
|
@ -257,8 +257,14 @@ Each team member who wants to run AI agents locally needs to:
|
|||
|
||||
```bash
|
||||
# Point CLI to your server
|
||||
#
|
||||
# For production deployments with TLS:
|
||||
export MULTICA_APP_URL=https://app.example.com
|
||||
export MULTICA_SERVER_URL=wss://api.example.com/ws
|
||||
#
|
||||
# For local deployments without TLS:
|
||||
# export MULTICA_APP_URL=http://localhost:3000
|
||||
# export MULTICA_SERVER_URL=ws://localhost:8080/ws
|
||||
|
||||
# Login (opens browser)
|
||||
multica login
|
||||
|
|
@ -267,6 +273,8 @@ Each team member who wants to run AI agents locally needs to:
|
|||
multica daemon start
|
||||
```
|
||||
|
||||
> **Note:** Use `https://` and `wss://` for production deployments behind a TLS-terminating reverse proxy. For local or development deployments without TLS, use `http://` and `ws://` instead.
|
||||
|
||||
The daemon auto-detects installed agent CLIs and registers itself with the server. When an agent is assigned a task in Multica, the daemon picks it up, creates an isolated workspace, runs the agent, and reports results back.
|
||||
|
||||
## Upgrading
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue