Skip to content

Latest commit

 

History

History
163 lines (93 loc) · 5.47 KB

README.md

File metadata and controls

163 lines (93 loc) · 5.47 KB

Banner

One-click deployment of the ChatGPT private proxy, power by Next.js, support SSE!

English | 简体中文

Introduction

This project is based on Next.js, use Rewriter to complete proxy function, only 2 lines of core code, combining Zeabur or Vercel can easily host your private proxy service

Before you start, you'd better check the How to use section to determine whether this project is applicable to you

ps: The SSE part of the code from chatgptProxyAPI

Quick jump

Deploy on your server

You must have a server and make sure your server can access ChatGPT

You need some knowledge about Docker

  1. Fork this repository for your own repository

fork

  1. Switch to the your forked project directory and run docker build -t chatgpt-proxy .

  2. then run docker run --name chatgpt-proxy -d -p 8000:3000 chatgpt-proxy

  3. open http://127.0.0.1:8000 on your browser

If you don't use Docker, you can also manually deploy it

Steps for manually deploy

Your nodejs version needs to be greater than or equal to 14

1. Pull this repo to the local

$ git pull https://github.com/imyuanx/chatgpt-proxy
$ cd chatgpt-proxy

2. Installations

$ pnpm install

3. Build

$ pnpm build

4. Running Services

$ pnpm start

Deploy on Zeabur

❗️⚠️❗️Warning: This project may violate the Never Fair Use - Proxies and VPNs entries under the Zeabur Terms of Use. Zeabur hosting this project is strongly not recommended!

❗️⚠️❗️Warning: If your account is punished due to the deployment of this project to Zeabur, please bear the consequences

Steps for deployment

❗️⚠️❗️Assuming that you have completely read the warning information and understand the possible risks and consequences, you can still continue to complete the deployment

Specific operations are as follows

  1. Fork this repository for your own repository
fork
  1. Add a new service on Zeabur console
step 1
  1. Add service and deploy from source code
step 2 step 2-1
  1. Select your forked repo
step 3
  1. Select main and deploy
step 4
  1. After the deployment is successful, Generate the domain name.
step 5
  1. Finally get your service
step 6

Deploy on Vercel

❗️⚠️❗️Warning: This project may violate the Never Fair Use - Proxies and VPNs entries under the Vercel Terms of Use. Vercel hosting this project is strongly not recommended!

❗️⚠️❗️Warning: If your account is punished due to the deployment of this project to Vercel, please bear the consequences

Steps for deployment

❗️⚠️❗️Assuming that you have completely read the warning information and understand the possible risks and consequences, you can still continue to complete the deployment

If you use Vercel deploy services, you must custom domain name, beacuse the custom domain name is not affected by the GFW, Specific operations are as follows

Deploy to Vercel

  1. Click the deploy button at the top
One-click deploy
  1. After deployment, the repository will be forked automatically for you, entering a custom repository name in the input field
Deploy
  1. After successful deployment, get your service
Alt text
  1. You must add a custom domain name for your service, otherwise you will not be able to access your service in the country
Domain

How to use

Whether you use Zeabur or Vercel, you will get the following proxy service after deployment

Proxy service

The resulting two addresses will be fully forwarded to https://api.openai.com and both will be domestically accessible, where .../proxy-sse supports SSE

You can use the proxy service in applications that support custom apis to invoke the "openai" interface domestically

Fro example, openai-translator:

Alt text

Back to top