wehub-resource-sync
126 lines
3.2 KiB
Markdown
126 lines
3.2 KiB
Markdown
# Deploy InsForge with Docker
|
|
|
|
## Prerequisites
|
|
|
|
- Docker and Docker Compose installed on your machine
|
|
|
|
## Setup InsForge
|
|
|
|
### Step 1: Download the Docker Compose file
|
|
|
|
```bash
|
|
wget https://raw.githubusercontent.com/insforge/insforge/main/deploy/docker-compose/docker-compose.yml
|
|
wget https://raw.githubusercontent.com/insforge/insforge/main/deploy/docker-compose/.env.example
|
|
mv .env.example .env
|
|
```
|
|
|
|
### Step 2: Start InsForge
|
|
|
|
```bash
|
|
docker compose up -d
|
|
```
|
|
|
|
### Step 3: Access InsForge
|
|
|
|
Open your browser and navigate to `http://localhost:7130`, you can see the InsForge dashboard as below:
|
|
|
|
<div align="center">
|
|
<img src="../assets/signin.png" alt="InsForge Dashboard" width="600">
|
|
</div>
|
|
|
|
## Running Multiple Instances
|
|
|
|
You can run multiple InsForge projects on the same host by using different ports and project names.
|
|
|
|
### Step 1: Create a separate env file for each project
|
|
|
|
```bash
|
|
cp .env.example .env.project1
|
|
cp .env.example .env.project2
|
|
```
|
|
|
|
### Step 2: Edit each env file with unique ports
|
|
|
|
**.env.project1** (default ports):
|
|
```
|
|
POSTGRES_PORT=5432
|
|
POSTGREST_PORT=5430
|
|
APP_PORT=7130
|
|
AUTH_PORT=7131
|
|
DENO_PORT=7133
|
|
```
|
|
|
|
**.env.project2** (different ports):
|
|
```
|
|
POSTGRES_PORT=5442
|
|
POSTGREST_PORT=5440
|
|
APP_PORT=7230
|
|
AUTH_PORT=7231
|
|
DENO_PORT=7233
|
|
```
|
|
|
|
Make sure each project has its own `JWT_SECRET` and `ROOT_ADMIN_PASSWORD`.
|
|
|
|
### Step 3: Start each project with a unique name
|
|
|
|
```bash
|
|
docker compose --env-file .env.project1 -p project1 up -d
|
|
docker compose --env-file .env.project2 -p project2 up -d
|
|
```
|
|
|
|
The `-p` flag gives each project isolated containers, volumes, and networks. The `--env-file` flag assigns unique ports so they don't conflict.
|
|
|
|
### Managing multiple instances
|
|
|
|
```bash
|
|
# Check status
|
|
docker compose --env-file .env.project1 -p project1 ps
|
|
|
|
# View logs
|
|
docker compose --env-file .env.project1 -p project1 logs -f
|
|
|
|
# Stop an instance
|
|
docker compose --env-file .env.project1 -p project1 down
|
|
|
|
# Stop and remove all data
|
|
docker compose --env-file .env.project1 -p project1 down -v
|
|
```
|
|
|
|
Each project has its own database, storage, and configuration. They are completely independent.
|
|
|
|
---
|
|
|
|
## Start using InsForge
|
|
|
|
### 1. Connect InsForge MCP
|
|
|
|
Open [InsForge Dashboard](http://localhost:7130), Follow the steps to connect InsForge MCP Server:
|
|
|
|
<div align="center">
|
|
<img src="../assets/connect.png" alt="Connect InsForge MCP" width="600">
|
|
</div>
|
|
|
|
### 2. Verify installation
|
|
|
|
To verify the connection, send the following prompt to your agent:
|
|
```
|
|
I'm using InsForge as my backend platform, call InsForge MCP's fetch-docs tool to learn about InsForge instructions.
|
|
```
|
|
|
|
### 3. Start building your project
|
|
|
|
Build your next todo app, Instagram clone, or online platform in seconds!
|
|
|
|
Sample Project Prompt:
|
|
|
|
```
|
|
Build an app similar to Reddit with community-based discussion threads using InsForge as the backend platform that has these features:
|
|
|
|
- Has a "Communities" list where users can browse or create communities
|
|
- Each community has its own posts feed
|
|
- Users can create posts with a title and body (text or image upload to InsForge storage)
|
|
- Users can comment on posts and reply to other comments
|
|
- Allows upvoting and downvoting for both posts and comments
|
|
- Shows vote counts and comment counts for each post
|
|
```
|