HiMarket Deployment Guide

1. Local Setup

Environment Dependencies: JDK 17, Node.js 18+, Maven 3.6+, MySQL 8.0+

Start Backend:

# Build project
mvn clean package -DskipTests

# Start backend service
java --add-opens java.base/java.util=ALL-UNNAMED \
     --add-opens java.base/java.lang=ALL-UNNAMED \
     --add-opens java.base/java.lang.reflect=ALL-UNNAMED \
     -Ddb.host=${DB_HOST} \
     -Ddb.port=${DB_PORT} \
     -Ddb.name=${DB_NAME} \
     -Ddb.username=${DB_USERNAME} \
     -Ddb.password=${DB_PASSWORD} \
     -jar himarket-bootstrap/target/himarket-bootstrap-1.0-SNAPSHOT.jar

# Backend API address: http://localhost:8080

Start Frontend:

# Start management console
cd himarket-web/himarket-admin
npm install
npm run dev
# Management console address: http://localhost:5174

# Start developer portal
cd himarket-web/himarket-frontend
npm install
npm run dev
# Developer portal address: http://localhost:5173

2. Docker Compose Deployment

Includes seven service components:

• mysql: Database service, providing data storage for backend services;
• himarket-server: Backend service, running on port 8081;
• himarket-admin: Management console interface, running on port 5174, for administrators to configure Portal;
• himarket-frontend: Frontend user interface, running on port 5173, for users to browse and use API Products;
• Higress: Higress all-in-one gateway service, running on ports 8443, 8082, 8001, with console running on port 8001 for user access;
• Redis: Higress cache service;
• Nacos: Nacos service, running on ports 8080, 8848, 9848, with console running on port 8080 for user access.

Installation Commands

Environment Dependencies: docker, docker compose, curl, jq

One-Click Startup: Use the deploy.sh script to complete full-stack deployment and data initialization of HiMarket, Higress, and Nacos.

# Clone project
git clone https://github.com/higress-group/himarket.git
cd himarket/deploy/docker/scripts

# Deploy full-stack services and initialize
./deploy.sh install

# Or deploy only Himarket services (without Nacos/Higress)
./deploy.sh himarket-only

# Uninstall all services
./deploy.sh uninstall

# Service addresses
# Management console address: http://localhost:5174
# Developer portal address: http://localhost:5173
# Backend API address: http://localhost:8081

The script will execute data initialization hooks after deployment: performs login data initialization, example MCP data initialization, and API product data initialization. Note that the script includes deployment and data initialization parts. Data initialization execution does not block deployment. If data initialization hooks fail, they can be retried in /scripts/hooks/post_ready.d. For example:

cd docker/scripts/hooks/post_ready.d

# Retry failed script
./10-init-nacos-admin.sh

Installation Configuration

All configurations are centralized in the scripts/data/.env file:

cd docker/scripts/data
vi .env

3. Cloud-Native Deployment with Helm

Helm is a package management system for automating Kubernetes software management and release. Through the Helm one-click deployment script, you can quickly deploy and install HiMarket+Higress+Nacos on a Kubernetes cluster, including ten service components:

• HiMarket:
  • himarket-server: HiMarket AI open platform backend service;
  • himarket-admin: HiMarket AI open platform management console, administrators configure Portal through this interface;
  • himarket-frontend: HiMarket AI open platform frontend service, users browse and use APIs through this interface;
  • mysql: Optional built-in database.
• Higress:
  • higress-console: Console, users browse and use Higress service through this interface;
  • higress-controller: Control plane component, responsible for managing configuration distribution;
  • higress-gateway: Data plane component, responsible for carrying data traffic;
  • redis-stack-server: Cache component.
• Nacos:
  • nacos: Nacos application;
  • nacos-mysql: Nacos database.

Service Type Description:

Default is LoadBalancer type service, suitable for cloud environments (Alibaba Cloud ACK, AWS EKS, etc.). If your environment does not support LoadBalancer (such as local minikube, self-built clusters), you can use NodePort or port forwarding to access. After configuring Himarket in the backend, resolve the domain name to the himarket-frontend service access address, and users can access the frontend site through the domain name.

Installation Commands

Environment Dependencies: kubectl, python3/python, curl, jq

One-Click Startup: Use the deploy.sh script to deploy HiMarket to a Kubernetes cluster.

# Clone project
git clone https://github.com/higress-group/himarket.git
cd himarket/deploy/helm/scripts

# Deploy full-stack services and initialize
./deploy.sh install

# Or deploy only Himarket services (without Nacos/Higress)
./deploy.sh himarket-only

# Uninstall
./deploy.sh uninstall

The script will execute data initialization hooks after deployment: performs login data initialization, example MCP data initialization, and API product data initialization. Note that the script includes deployment and data initialization parts. Data initialization execution does not block deployment. If data initialization hooks fail, they can be retried in /scripts/hooks/post_ready.d. For example:

cd helm/scripts/hooks/post_ready.d

# Retry failed script
./10-init-nacos-admin.sh

Installation Configuration

Related configurations are centralized in the scripts/data/.env file:

cd helm/scripts/data
vi .env

Note: HiMarket’s Helm package is adapted for Alibaba Cloud ACK cluster use. The storage class persistence.storageClass: “alicloud-disk-essd” value in the /helm/values.yaml file needs to be adjusted according to the actual environment.

4. Cloud Platform Deployment (Alibaba Cloud)

Alibaba Cloud Computing Nest supports the out-of-the-box version of this project, with one-click deployment of the community edition: