chuan/CLIProxyAPI
1
0
Fork 0
mirror of https://github.com/router-for-me/CLIProxyAPI.git synced 2026-02-03 04:50:52 +08:00
Code Issues Packages Projects Releases Wiki Activity

Refactor docker-compose config for simplicity and consistency

Browse Source
This commit is contained in:
hkfires
2025-09-07 11:35:54 +08:00
parent 47b5ebfc43
commit 5aba4ca1b1
7 changed files with 49 additions and 47 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
README.md
View File

@@ -505,7 +505,7 @@ docker run --rm -p 8317:8317 -v /path/to/your/config.yaml:/CLIProxyAPI/config.ya
2. Create a `config.yaml` from `config.example.yaml` and customize it.
3. Build and start the services using the interactive build scripts:
3. Run the interactive script to start the service:
- For Windows (PowerShell):
```powershell
.\docker-build.ps1
@@ -514,9 +514,9 @@ docker run --rm -p 8317:8317 -v /path/to/your/config.yaml:/CLIProxyAPI/config.ya
```bash
bash docker-build.sh
```
The script will prompt you to choose an environment:
- **Option 1: Local Development**: Builds the Docker image from the source and starts the services.
- **Option 2: Remote Deployment**: Pulls the pre-built image specified in `docker-compose.remote.yml` and starts the services.
The script will prompt you to choose how to run the application:
- **Option 1: Run using Pre-built Image (Recommended)**: Pulls the latest official image from the registry and starts the container. This is the easiest way to get started.
- **Option 2: Build from Source and Run (For Developers)**: Builds the image from the local source code, tags it as `cli-proxy-api:local`, and then starts the container. This is useful if you are making changes to the source code.
4. To authenticate with providers, run the login command inside the container:
- **Gemini**: `docker compose exec cli-proxy-api /CLIProxyAPI/CLIProxyAPI -no-browser --login`