chatgpt-web

A third-party ChatGPT Web UI page built with Express and Vue3, through the official OpenAI completion API. / 用 Express 和 Vue3 搭建的第三方 ChatGPT 前端页面, 基于 OpenAI 官方 completion API.

1,683

449

1,683

153

View on GitHub

Top Related Projects

NextChat

78,774

ChuanhuChatGPT

15,346

GUI for ChatGPT API and many LLMs. Supports agents, file-based QA, GPT finetuning and query with web search. All with a neat UI.

ChatGPT

53,461

🔮 ChatGPT Desktop Application (Mac, Windows and Linux)

gpt4free

63,126

The official gpt4free repository | various collection of powerful language models

Quick Overview

ChatGPT-Web is an open-source project that provides a web interface for interacting with OpenAI's ChatGPT model. It allows users to deploy their own ChatGPT-like web application with customizable features and a user-friendly interface.

Pros

Easy to deploy and self-host
Customizable UI and features
Supports multiple API endpoints (OpenAI, Azure, Claude, etc.)
Active community and frequent updates

Cons

Requires API key from OpenAI or other supported providers
May have higher latency compared to official ChatGPT interface
Limited advanced features compared to paid ChatGPT Plus
Potential for misuse if not properly configured

Getting Started

Clone the repository:

git clone https://github.com/Chanzhaoyu/chatgpt-web.git

Install dependencies:
```
cd chatgpt-web
pnpm install
```
Configure environment variables: Create a .env file in the root directory and add your OpenAI API key:
```
OPENAI_API_KEY=your_api_key_here
```
Start the development server:
```
pnpm dev
```
Build for production:
```
pnpm build
```

For more detailed instructions and configuration options, refer to the project's README.md file.

Competitor Comparisons

chatgpt-demo

8,012

Minimal web UI for ChatGPT.

Pros of chatgpt-demo

Lightweight and easy to deploy
Supports multiple languages out of the box
Clean and modern user interface

Cons of chatgpt-demo

Limited customization options
Fewer advanced features compared to chatgpt-web
May require more setup for complex use cases

Code Comparison

chatgpt-demo:

import { defineConfig } from 'vite'
import vue from '@vitejs/plugin-vue'
import { VitePWA } from 'vite-plugin-pwa'

export default defineConfig({
  plugins: [vue(), VitePWA()],
})

chatgpt-web:

const express = require('express');
const path = require('path');
const app = express();

app.use(express.static(path.join(__dirname, 'public')));
app.listen(3000, () => console.log('Server running on port 3000'));

The code snippets show different approaches:

chatgpt-demo uses Vite for building and Vue.js for the frontend
chatgpt-web uses Express.js for serving static files and handling server-side logic

Both projects aim to provide a web interface for ChatGPT, but they differ in their implementation and feature sets. chatgpt-demo focuses on simplicity and ease of use, while chatgpt-web offers more advanced features and customization options.

chatgpt-web

31,723

用 Express 和 Vue3 搭建的 ChatGPT 演示网页

Pros of chatgpt-web

More active development with frequent updates and bug fixes
Supports multiple API endpoints, including Azure OpenAI
Offers a wider range of customization options for appearance and functionality

Cons of chatgpt-web

Slightly more complex setup process due to additional features
May have higher resource requirements for hosting and deployment
Some users report occasional stability issues with certain features

Code Comparison

chatgpt-web:

const apiKey = import.meta.env.OPENAI_API_KEY
const model = import.meta.env.OPENAI_API_MODEL
const temperature = import.meta.env.OPENAI_API_TEMPERATURE

chatgpt-web-dev:

const API_KEY = process.env.OPENAI_API_KEY
const MODEL = 'gpt-3.5-turbo'
const TEMPERATURE = 0.7

The code snippets show differences in environment variable handling and default model settings. chatgpt-web uses Vite's import.meta.env for configuration, while chatgpt-web-dev uses Node.js process.env. chatgpt-web also allows for more flexible model and temperature settings through environment variables.

NextChat

78,774

Pros of NextChat

Built with Next.js, offering better performance and SEO optimization
More modern UI with a sleek, responsive design
Supports multiple API endpoints and models

Cons of NextChat

Potentially more complex setup due to Next.js framework
May require more resources to run compared to the simpler chatgpt-web

Code Comparison

NextChat (TypeScript):

import { NextApiRequest, NextApiResponse } from 'next'
import { ChatGPTAPI } from 'chatgpt'

export default async function handler(req: NextApiRequest, res: NextApiResponse) {
  const api = new ChatGPTAPI({ apiKey: process.env.OPENAI_API_KEY })
  // ... rest of the code
}

chatgpt-web (JavaScript):

const express = require('express')
const { Configuration, OpenAIApi } = require('openai')

const app = express()
const configuration = new Configuration({ apiKey: process.env.OPENAI_API_KEY })
const openai = new OpenAIApi(configuration)

The code snippets show that NextChat uses Next.js API routes and TypeScript, while chatgpt-web uses Express.js and plain JavaScript. NextChat's approach may offer better type safety and integration with the Next.js ecosystem, but chatgpt-web's setup is simpler and more straightforward for developers familiar with Express.js.

Both projects aim to provide a web interface for ChatGPT, but NextChat offers a more feature-rich experience with its modern tech stack, while chatgpt-web focuses on simplicity and ease of use.

ChuanhuChatGPT

15,346

GUI for ChatGPT API and many LLMs. Supports agents, file-based QA, GPT finetuning and query with web search. All with a neat UI.

Pros of ChuanhuChatGPT

More extensive language support, including Chinese
Advanced features like API key management and model selection
Active development with frequent updates

Cons of ChuanhuChatGPT

More complex setup process
Heavier resource requirements due to additional features

Code Comparison

ChuanhuChatGPT:

def predict(self, input, chatbot, stream = False, use_websearch=False, files = []):
    if stream:
        return self.predict_stream(input, chatbot, use_websearch, files)
    else:
        return self.predict_no_stream(input, chatbot, use_websearch, files)

chatgpt-web:

async function sendMessage(message) {
  const response = await fetch('/api/chat', {
    method: 'POST',
    headers: { 'Content-Type': 'application/json' },
    body: JSON.stringify({ message }),
  });
  return response.json();
}

The code snippets highlight the different approaches:

ChuanhuChatGPT uses Python and offers more flexibility with streaming and web search options
chatgpt-web uses JavaScript and focuses on a simpler API call structure

Overall, ChuanhuChatGPT offers more features and language support but requires more setup, while chatgpt-web provides a simpler, more lightweight solution.

ChatGPT

53,461

🔮 ChatGPT Desktop Application (Mac, Windows and Linux)

Pros of ChatGPT

Desktop application with cross-platform support (Windows, macOS, Linux)
Offers additional features like export/import of chat history and proxy settings
Regular updates and active development

Cons of ChatGPT

Requires installation and system resources
May have a steeper learning curve for non-technical users
Limited customization options compared to web-based alternatives

Code Comparison

ChatGPT (Tauri-based desktop app):

#[tauri::command]
fn greet(name: &str) -> String {
    format!("Hello, {}! You've been greeted from Rust!", name)
}

chatgpt-web (Vue.js-based web app):

<template>
  <div>
    <h1>{{ greeting }}</h1>
    <input v-model="name" @keyup.enter="greet" />
  </div>
</template>

<script>
export default {
  data() {
    return {
      name: '',
      greeting: 'Enter your name'
    }
  },
  methods: {
    greet() {
      this.greeting = `Hello, ${this.name}!`
    }
  }
}
</script>

The code comparison highlights the different approaches: ChatGPT uses Rust for backend logic, while chatgpt-web utilizes Vue.js for frontend interactivity. This reflects the fundamental difference between a desktop application and a web-based solution.

gpt4free

63,126

The official gpt4free repository | various collection of powerful language models

Pros of gpt4free

Offers free access to GPT-4 and other AI models without API keys
Supports multiple providers and model types
Includes examples and implementations in various programming languages

Cons of gpt4free

May have legal and ethical concerns due to unauthorized API usage
Less stable and reliable compared to official APIs
Requires more frequent updates to maintain functionality

Code Comparison

gpt4free:

from g4f import ChatCompletion

response = ChatCompletion.create(
    model="gpt-3.5-turbo",
    messages=[{"role": "user", "content": "Hello, how are you?"}]
)
print(response)

chatgpt-web:

const { Configuration, OpenAIApi } = require("openai");
const configuration = new Configuration({
  apiKey: process.env.OPENAI_API_KEY,
});
const openai = new OpenAIApi(configuration);

The gpt4free code snippet demonstrates how to use the library to generate responses without an API key, while the chatgpt-web code shows the setup for using the official OpenAI API with proper authentication.

Convert designs to code with AI

Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.

Try Visual Copilot

README

ChatGPT Web

ä¸æ | English

è¯´æ

[!IMPORTANT] æ¤é¡¹ç® Fork èª Chanzhaoyu/chatgpt-web

ç±äºåé¡¹ç®ä½èä¸æ¿æå¼å¥å¯¹æ°æ®åºçä¾èµ æå¶ä½è¯¥æ°¸ä¹ååç¬ç«å¼å è¯¦è§è®¨è®º

åæ¬¡æè°¢ Chanzhaoyu å¤§ä½¬å¯¹å¼æºçè´¡ç® ð

æ°å¢äºé¨åç¹è²åè½:

[â] æ³¨å & ç»å½ & éç½®å¯ç & 2FA

[â] åæ¥åå²ä¼è¯

[â] åç«¯é¡µé¢è®¾ç½®apikey

[â] èªå®ä¹ææè¯

[â] æ¯ä¸ªä¼è¯è®¾ç½®ç¬æ Prompt

[â] ç¨æ·ç®¡ç

[â] å¤ Key éæº

[â] å¯¹è¯æ°ééå¶ & è®¾ç½®ä¸åç¨æ·å¯¹è¯æ°é & åæ¢æ°é

[â] éè¿ auth proxy åè½å®ç°ssoç»å½ (éåç¬¬ä¸æ¹èº«ä»½éªè¯ååä»£ç å¯å®ç°æ¯æ LDAP/OIDC/SAML çåè®®ç»å½)

[!CAUTION] å£°æï¼æ¤é¡¹ç®åªåå¸äº Githubï¼åºäº MIT åè®®ï¼åè´¹ä¸ä½ä¸ºå¼æºå¦ä¹ ä½¿ç¨ãå¹¶ä¸ä¸ä¼æä»»ä½å½¢å¼çåå·ãä»è´¹æå¡ãè®¨è®ºç¾¤ãè®¨è®ºç»çè¡ä¸ºãè°¨é²åéªã

æªå¾

cover3 cover cover2 cover3 cover3 cover3 cover3 userlimit setmanuallimit giftcarddb

ChatGPT Web

ä»ç»

æ¯æåæ¨¡åï¼æä¾äºä¸¤ç§éå®æ¹ ChatGPT API æ¹æ³

æ¹å¼	åè´¹ï¼	å¯é æ§	è´¨é
`ChatGPTAPI(gpt-3.5-turbo-0301)`	å¦	å¯é	ç¸å¯¹è¾ç¬¨
`ChatGPTUnofficialProxyAPI(ç½é¡µ accessToken)`	æ¯	ç¸å¯¹ä¸å¯é	èªæ

å¯¹æ¯ï¼

ChatGPTAPI ä½¿ç¨ gpt-3.5-turbo éè¿ OpenAI å®æ¹ API è°ç¨ ChatGPT
ChatGPTUnofficialProxyAPI ä½¿ç¨éå®æ¹ä»£çæå¡å¨è®¿é® ChatGPT çåç«¯APIï¼ç»è¿Cloudflareï¼ä¾èµäºç¬¬ä¸æ¹æå¡å¨ï¼å¹¶ä¸æéçéå¶ï¼

è¦åï¼

ä½ åºè¯¥é¦åä½¿ç¨ API æ¹å¼
ä½¿ç¨ API æ¶ï¼å¦æç½ç»ä¸éï¼é£æ¯å½åè¢«å¢äºï¼ä½ éè¦èªå»ºä»£çï¼ç»å¯¹ä¸è¦ä½¿ç¨å«äººçå¬å¼ä»£çï¼é£æ¯å±é©çã
ä½¿ç¨ accessToken æ¹å¼æ¶ååä»£çå°åç¬¬ä¸æ¹æ´é²æ¨çè®¿é®ä»¤çï¼è¿æ ·ååºè¯¥ä¸ä¼äº§çä»»ä½ä¸è¯å½±åï¼ä½å¨ä½¿ç¨è¿ç§æ¹æ³ä¹åè¯·èèé£é©ã
ä½¿ç¨ accessToken æ¶ï¼ä¸ç®¡ä½ æ¯å½åè¿æ¯å½å¤çæºå¨ï¼é½ä¼ä½¿ç¨ä»£çãé»è®¤ä»£çä¸º pengzhile å¤§ä½¬ç https://ai.fakeopen.com/api/conversationï¼è¿ä¸æ¯åé¨ä¹ä¸æ¯çå¬ï¼é¤éä½ æè½åèªå·±ç¿»è¿ CF éªè¯ï¼ç¨åè¯·ç¥æãç¤¾åºä»£çï¼æ³¨æï¼åªæè¿ä¸¤ä¸ªæ¯æ¨èï¼å¶ä»ç¬¬ä¸æ¹æ¥æºï¼è¯·èªè¡çå«ï¼
æé¡¹ç®åå¸å°å¬å±ç½ç»æ¶ï¼ä½ åºè¯¥è®¾ç½® AUTH_SECRET_KEY åéæ·»å ä½ çå¯ç è®¿é®æéï¼ä½ ä¹åºè¯¥ä¿®æ¹ index.html ä¸ç titleï¼é²æ¢è¢«å³é®è¯æç´¢å°ã

åæ¢æ¹å¼ï¼

è¿å¥ service/.env.example æä»¶ï¼å¤å¶åå®¹å° service/.env æä»¶
ä½¿ç¨ OpenAI API Key è¯·å¡«å OPENAI_API_KEY åæ®µ (è·å apiKey)
ä½¿ç¨ Web API è¯·å¡«å OPENAI_ACCESS_TOKEN åæ®µ (è·å accessToken)
åæ¶åå¨æ¶ä»¥ OpenAI API Key ä¼å

ç¯å¢åéï¼

å¨é¨åæ°åéè¯·æ¥çæè¿é

/service/.env.example

å¾å®ç°è·¯çº¿

[â] åæ¨¡å

[â] å¤ä¼è¯å¨ååä¸ä¸æé»è¾

[â] å¯¹ä»£ç çæ¶æ¯ç±»åçæ ¼å¼åç¾åå¤ç

[â] æ¯æç¨æ·ç»å½æ³¨å

[â] åç«¯é¡µé¢è®¾ç½® apikey çä¿¡æ¯

[â] æ°æ®å¯¼å¥ãå¯¼åº

[â] ä¿åæ¶æ¯å°æ¬å°å¾ç

[â] çé¢å¤è¯è¨

[â] çé¢ä¸»é¢

[â] More...

åç½®è¦æ±

Node

node éè¦ ^16 || ^18 || ^20 || ^22 çæ¬ï¼ä½¿ç¨ nvm å¯ç®¡çæ¬å°å¤ä¸ª node çæ¬

node -v

PNPM

å¦æä½ æ²¡æå®è£è¿ pnpm

npm install pnpm -g

å¡«åå¯é¥

è·å Openai Api Key æ accessToken å¹¶å¡«åæ¬å°ç¯å¢åé è·³è½¬

# service/.env æä»¶

# OpenAI API Key - https://platform.openai.com/overview
OPENAI_API_KEY=

# change this to an `accessToken` extracted from the ChatGPT site's `https://chat.openai.com/api/auth/session` response
OPENAI_ACCESS_TOKEN=

å®è£ä¾èµ

ä¸ºäºç®ä¾¿ åç«¯å¼åäººå çäºè§£è´æï¼æä»¥å¹¶æ²¡æéç¨åç«¯ workspace æ¨¡å¼ï¼èæ¯åæä»¶å¤¹åæ¾ãå¦æåªéè¦åç«¯é¡µé¢åäºæ¬¡å¼åï¼å é¤ service æä»¶å¤¹å³å¯ã

åç«¯

è¿å¥æä»¶å¤¹ /service è¿è¡ä»¥ä¸å½ä»¤

pnpm install

åç«¯

æ ¹ç®å½ä¸è¿è¡ä»¥ä¸å½ä»¤

pnpm bootstrap

æµè¯ç¯å¢è¿è¡

åç«¯æå¡

è¿å¥æä»¶å¤¹ /service è¿è¡ä»¥ä¸å½ä»¤

pnpm start

åç«¯ç½é¡µ

æ ¹ç®å½ä¸è¿è¡ä»¥ä¸å½ä»¤

pnpm dev

ç¯å¢åé

API å¯ç¨ï¼

OPENAI_API_KEY å OPENAI_ACCESS_TOKEN äºéä¸
OPENAI_API_BASE_URL è®¾ç½®æ¥å£å°åï¼å¯éï¼é»è®¤ï¼https://api.openai.com
OPENAI_API_DISABLE_DEBUG è®¾ç½®æ¥å£å³é debug æ¥å¿ï¼å¯éï¼é»è®¤ï¼empty ä¸å³é

ACCESS_TOKEN å¯ç¨ï¼

OPENAI_ACCESS_TOKEN å OPENAI_API_KEY äºéä¸ï¼åæ¶åå¨æ¶ï¼OPENAI_API_KEY ä¼å
API_REVERSE_PROXY è®¾ç½®ååä»£çï¼å¯éï¼é»è®¤ï¼https://ai.fakeopen.com/api/conversationï¼ç¤¾åºï¼æ³¨æï¼åªæè¿ä¸¤ä¸ªæ¯æ¨èï¼å¶ä»ç¬¬ä¸æ¹æ¥æºï¼è¯·èªè¡çå«ï¼

éç¨ï¼

AUTH_SECRET_KEY è®¿é®æéå¯é¥ï¼å¯é
MAX_REQUEST_PER_HOUR æ¯å°æ¶æå¤§è¯·æ±æ¬¡æ°ï¼å¯éï¼é»è®¤æ é
TIMEOUT_MS è¶æ¶ï¼åä½æ¯«ç§ï¼å¯é
SOCKS_PROXY_HOST å SOCKS_PROXY_PORT ä¸èµ·æ¶çæï¼å¯é
SOCKS_PROXY_PORT å SOCKS_PROXY_HOST ä¸èµ·æ¶çæï¼å¯é
HTTPS_PROXY æ¯æ httpï¼https, socks5ï¼å¯é

æå

ä½¿ç¨ Docker

Docker åæ°ç¤ºä¾

docker

Docker build & Run

GIT_COMMIT_HASH=`git rev-parse HEAD`
RELEASE_VERSION=`git branch --show-current`
docker build --build-arg GIT_COMMIT_HASH=${GIT_COMMIT_HASH} --build-arg RELEASE_VERSION=${RELEASE_VERSION} -t chatgpt-web .

# åå°è¿è¡
# å¦æå¨å®¿ä¸»æºè¿è¡ mongodb åä½¿ç¨ MONGODB_URL=mongodb://host.docker.internal:27017/chatgpt
docker run --name chatgpt-web --rm -it -p 3002:3002 --env OPENAI_API_KEY=your_api_key --env MONGODB_URL=your_mongodb_url chatgpt-web

# åå°è¿è¡
docker run --name chatgpt-web -d -p 127.0.0.1:3002:3002 --env OPENAI_API_KEY=your_api_key --env MONGODB_URL=your_mongodb_url chatgpt-web

# è¿è¡å°å
http://localhost:3002/

Docker compose

Hub å°å

version: '3'

services:
  app:
    image: chatgptweb/chatgpt-web # æ»æ¯ä½¿ç¨latest,æ´æ°æ¶éæ°pullè¯¥tagéåå³å¯
    container_name: chatgptweb
    restart: unless-stopped
    ports:
      - 3002:3002
    depends_on:
      - database
    environment:
      TZ: Asia/Shanghai
      # æ¯å°æ¶æå¤§è¯·æ±æ¬¡æ°ï¼å¯éï¼é»è®¤æ é
      MAX_REQUEST_PER_HOUR: 0
      # è®¿é®jwtå å¯åæ°ï¼å¯é ä¸ä¸ºç©ºååè®¸ç»å½ åæ¶éè¦è®¾ç½® MONGODB_URL
      AUTH_SECRET_KEY: xxx
      # ç½ç«åç§°
      SITE_TITLE: ChatGpt Web
      # mongodb çè¿æ¥åç¬¦ä¸²
      MONGODB_URL: 'mongodb://chatgpt:xxxx@database:27017'
      # å¼å¯æ³¨åä¹å å¯ç å å¯çç
      PASSWORD_MD5_SALT: xxx
      # å¼å¯æ³¨åä¹å è¶çº§ç®¡çé®ç®±
      ROOT_USER: me@example.com
      # ç½ç«æ¯å¦å¼å¯æ³¨å å¿é¡»å¼å¯, å¦åç®¡çåé½æ²¡æ³æ³¨å, å¯åç»å³é
      REGISTER_ENABLED: true
      # æ´å¤éç½®, å¨è¿è¡å, æ³¨åç®¡çå, å¨ç®¡çåé¡µé¢ä¸è®¾ç½®
    links:
      - database

  database:
    image: mongo
    container_name: chatgptweb-database
    restart: unless-stopped
    ports:
      - '27017:27017'
    expose:
      - '27017'
    volumes:
      - mongodb:/data/db
    environment:
      MONGO_INITDB_ROOT_USERNAME: chatgpt
      MONGO_INITDB_ROOT_PASSWORD: xxxx
      MONGO_INITDB_DATABASE: chatgpt

volumes:
  mongodb: {}

OPENAI_API_BASE_URL å¯éï¼è®¾ç½® OPENAI_API_KEY æ¶å¯ç¨

é²æ¢ç¬è«æå

nginx

å°ä¸é¢éç½®å¡«å¥nginxéç½®æä»¶ä¸ï¼å¯ä»¥åè docker-compose/nginx/nginx.conf æä»¶ä¸æ·»å åç¬è«çæ¹æ³

    # é²æ¢ç¬è«æå
    if ($http_user_agent ~* "360Spider|JikeSpider|Spider|spider|bot|Bot|2345Explorer|curl|wget|webZIP|qihoobot|Baiduspider|Googlebot|Googlebot-Mobile|Googlebot-Image|Mediapartners-Google|Adsbot-Google|Feedfetcher-Google|Yahoo! Slurp|Yahoo! Slurp China|YoudaoBot|Sosospider|Sogou spider|Sogou web spider|MSNBot|ia_archiver|Tomato Bot|NSPlayer|bingbot"){
      return 403;
    }

ä½¿ç¨ Railway é¨ç½²

åèè¿ä¸ª issue è¯¦ç»æç¨ https://github.com/Kerwin1202/chatgpt-web/issues/266

æ³¨æ: Railway ä¿®æ¹ç¯å¢åéä¼éæ° Deploy

æå¨æå

åç«¯æå¡

å¦æä½ ä¸éè¦æ¬é¡¹ç®ç node æ¥å£ï¼å¯ä»¥çç¥å¦ä¸æä½

å¤å¶ service æä»¶å¤¹å°ä½ æ node æå¡ç¯å¢çæå¡å¨ä¸ã

# å®è£
pnpm install

# æå
pnpm build

# è¿è¡
pnpm prod

PS: ä¸è¿è¡æåï¼ç´æ¥å¨æå¡å¨ä¸è¿è¡ pnpm start ä¹å¯

åç«¯ç½é¡µ

1ãä¿®æ¹æ ¹ç®å½ä¸ .env æä»¶ä¸ç VITE_GLOB_API_URL ä¸ºä½ çå®éåç«¯æ¥å£å°å

åèä¿¡æ¯

pnpm build

Auth Proxy Mode

[!WARNING] è¯¥åè½ä»éç¨äºæç¸å³ç»éªçè¿ç»´äººåå¨éæä¼ä¸åé¨è´¦å·ç®¡çç³»ç»æ¶é¨ç½² éç½®ä¸å½å¯è½ä¼å¯¼è´å®å¨é£é©

è®¾ç½®ç¯å¢åé AUTH_PROXY_ENABLED=true å³å¯å¼å¯ auth proxy æ¨¡å¼

å¸¸è§é®é¢

Q: ä¸ºä»ä¹ Git æäº¤æ»æ¯æ¥éï¼

A: å ä¸ºææäº¤ä¿¡æ¯éªè¯ï¼è¯·éµå¾ª Commit æå

Q: å¦æåªä½¿ç¨åç«¯é¡µé¢ï¼å¨åªéæ¹è¯·æ±æ¥å£ï¼

A: æ ¹ç®å½ä¸ .env æä»¶ä¸ç VITE_GLOB_API_URL åæ®µã

Q: æä»¶ä¿åæ¶å¨é¨ççº¢?

A: vscode è¯·å®è£é¡¹ç®æ¨èæä»¶ï¼ææå¨å®è£ Eslint æä»¶ã

Q: åç«¯æ²¡ææåæºææï¼

A: ä¸ç§å¯è½åå æ¯ç»è¿ Nginx ååä»£çï¼å¼å¯äº bufferï¼å Nginx ä¼å°è¯ä»åç«¯ç¼å²ä¸å®å¤§å°çæ°æ®ååéç»æµè§å¨ãè¯·å°è¯å¨åä»£åæ°åæ·»å proxy_buffering off;ï¼ç¶åéè½½ Nginxãå¶ä» web server éç½®åçã

åä¸è´¡ç®

è´¡ç®ä¹åè¯·åéè¯» è´¡ç®æå

æè°¢ææåè¿è´¡ç®çäºº!

Star åå²

èµå©

WeChat Pay

Alipay

License

Top Related Projects

Convert designs to code with AI

Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.

Try Visual Copilot

Top Related Projects

Quick Overview

Pros

Cons

Getting Started

Competitor Comparisons

Pros of chatgpt-demo

Cons of chatgpt-demo

Code Comparison

Pros of chatgpt-web

Cons of chatgpt-web

Code Comparison

Pros of NextChat

Cons of NextChat

Code Comparison

Pros of ChuanhuChatGPT

Cons of ChuanhuChatGPT

Code Comparison

Pros of ChatGPT

Cons of ChatGPT

Code Comparison

Pros of gpt4free

Cons of gpt4free

Code Comparison

Convert designs to code with AI

README

ChatGPT Web

è¯´æ

æªå¾

ä»ç»

å¾ å®ç°è·¯çº¿

åç½®è¦æ±

Node

PNPM

å¡«åå¯é¥

å®è£ ä¾èµ

åç«¯

åç«¯

æµè¯ç¯å¢è¿è¡

åç«¯æå¡

åç«¯ç½é¡µ

ç¯å¢åé

æå

ä½¿ç¨ Docker

Docker åæ°ç¤ºä¾

Docker build & Run

Docker compose

é²æ­¢ç¬è«æå

ä½¿ç¨ Railway é¨ç½²

æå¨æå

åç«¯æå¡

åç«¯ç½é¡µ

Auth Proxy Mode

å¸¸è§é®é¢

åä¸è´¡ç®

Star åå²

èµå©

License

Top Related Projects

Convert designs to code with AI

è¯´æ

æªå¾

ä»ç»

å¾å®ç°è·¯çº¿

åç½®è¦æ±

å¡«åå¯é¥

å®è£ä¾èµ

åç«¯

åç«¯

æµè¯ç¯å¢è¿è¡

åç«¯æå¡

åç«¯ç½é¡µ

ç¯å¢åé

æå

ä½¿ç¨ Docker

Docker åæ°ç¤ºä¾

é²æ¢ç¬è«æå

ä½¿ç¨ Railway é¨ç½²

æå¨æå

åç«¯æå¡

åç«¯ç½é¡µ

å¸¸è§é®é¢

åä¸è´¡ç®

Star åå²

èµå©