mu is a multi-protocol user synchronization tool.
Configuration is done via environment variables. The following environment variables are supported:
| Environment Variable | Description | Example |
|---|---|---|
MU_API_BASE_URL |
Base URL for the API | https://api.example.com |
MU_API_TOKEN |
API access token | your-api-token |
MU_TROJAN_ADDRS |
Comma-separated list of Trojan server addresses | trojan1.example.com,trojan2.example.com |
MU_V2FLY_ADDRS |
Comma-separated list of V2Fly server addresses | v2fly1.example.com,v2fly2.example.com |
# Set API information
export MU_API_BASE_URL="https://api.example.com"
export MU_API_TOKEN="your-api-token"
# Set Trojan server addresses
export MU_TROJAN_ADDRS="trojan1.example.com,trojan2.example.com"
# Set V2Fly server addresses
export MU_V2FLY_ADDRS="v2fly1.example.com,v2fly2.example.com"You can use Docker Compose to run mu in a containerized environment. Here's an example docker-compose.yml file:
version: '3.8'
services:
mu:
image: ghcr.io/icebase/mu
container_name: mu
restart: unless-stopped
environment:
- MU_API_BASE_URL=https://api.example.com
- MU_API_TOKEN=your-api-token
- MU_TROJAN_ADDRS=trojan1.example.com,trojan2.example.com
- MU_V2FLY_ADDRS=v2fly1.example.com,v2fly2.example.com
networks:
- mu-network
networks:
mu-network:
driver: bridge- Create a
docker-compose.ymlfile with the configuration above - Update the environment variables with your actual values
- Run the container:
# Start the service
docker-compose up -d
# View logs
docker-compose logs -f mu
# Stop the service
docker-compose down