mirror of
https://github.com/eliasstepanik/core.git
synced 2026-01-10 08:48:29 +00:00
fix: docker docs
This commit is contained in:
parent
c1ccb2bb23
commit
b1569aafce
@ -32,10 +32,6 @@ To run CORE, you will need:
|
||||
- 8+ GB RAM
|
||||
- 20+ GB Storage
|
||||
|
||||
**Background Jobs Machine (if running separately):**
|
||||
- 2+ vCPU
|
||||
- 4+ GB RAM
|
||||
- 10+ GB Storage
|
||||
|
||||
## Deployment Options
|
||||
|
||||
@ -47,7 +43,7 @@ CORE offers two deployment approaches depending on your needs:
|
||||
|
||||
### Combined Setup
|
||||
|
||||
For self deployment with both CORE and Trigger.dev running together:
|
||||
For self deployment:
|
||||
|
||||
1. Clone core repository
|
||||
```bash
|
||||
|
||||
@ -48,10 +48,16 @@ Environment variables for the CORE webapp container.
|
||||
| `MODEL` | No | gpt-4-turbo-2024-04-09 | Default language model |
|
||||
| `EMBEDDING_MODEL` | No | text-embedding-3-small | Model for text embeddings |
|
||||
| `OLLAMA_URL` | No | http://ollama:11434 | Ollama server URL for local models |
|
||||
| **Background Jobs - Trigger.dev** | | | |
|
||||
| `TRIGGER_PROJECT_ID` | Yes | — | Trigger.dev project identifier |
|
||||
| `TRIGGER_SECRET_KEY` | Yes | — | Trigger.dev authentication secret |
|
||||
| `TRIGGER_API_URL` | Yes | http://host.docker.internal:8030 | Trigger.dev API endpoint (use localhost:8030 for local, api.trigger.dev for cloud) |
|
||||
| **Background Jobs** | | | |
|
||||
| `QUEUE_PROVIDER` | No | trigger | Queue provider: "trigger" for Trigger.dev or "bullmq" for BullMQ (Redis-based) |
|
||||
| `TRIGGER_PROJECT_ID` | Conditional | — | Trigger.dev project identifier (required only when QUEUE_PROVIDER=trigger) |
|
||||
| `TRIGGER_SECRET_KEY` | Conditional | — | Trigger.dev authentication secret (required only when QUEUE_PROVIDER=trigger) |
|
||||
| `TRIGGER_API_URL` | Conditional | http://host.docker.internal:8030 | Trigger.dev API endpoint (required only when QUEUE_PROVIDER=trigger) |
|
||||
| `TRIGGER_DB` | No | trigger | Database name for Trigger.dev |
|
||||
| **Telemetry** | | | |
|
||||
| `POSTHOG_PROJECT_KEY` | No | phc_SwfGIzzX5gh5bazVWoRxZTBhkr7FwvzArS0NRyGXm1a | PostHog project key for usage analytics |
|
||||
| `TELEMETRY_ENABLED` | No | true | Enable (true) or disable (false) telemetry collection |
|
||||
| `TELEMETRY_ANONYMOUS` | No | false | Send anonymous telemetry (true) or include user email (false) |
|
||||
|
||||
|
||||
## Security Considerations
|
||||
|
||||
@ -29,7 +29,6 @@ The self-hosted version of CORE is composed of several containers that you run o
|
||||
- **Webapp**: The main application container, responsible for serving the user interface and orchestrating memory operations.
|
||||
- **PostgreSQL**: Stores metadata, user accounts, and configuration data.
|
||||
- **Neo4j**: Graph database used for storing and querying the memory graph.
|
||||
- **[Trigger](https://trigger.dev/)**: Manages background jobs and workflows, such as data ingestion and memory formation. We use Trigger to reliably handle all background processing.
|
||||
- **Redis**: Provides caching and session management.
|
||||
|
||||
This modular architecture allows you to scale each service as needed and gives you full control over your deployment.
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user