chore: rename env file

This commit is contained in:
Tianzhou Chen
2023-12-17 21:34:15 +08:00
parent 8d02dba90e
commit 2984efaa7a
6 changed files with 7 additions and 7 deletions

View File

@ -82,7 +82,7 @@ docker run --name sqlchat --platform linux/amd64 --env NEXTAUTH_SECRET=xxx --env
1. Haga una copia del archivo de variables de entorno de ejemplo:
```bash
cp .env.use-db .env
cp .env.usedb .env
```
1. Generar el cliente prisma a partir del modelo.

View File

@ -59,9 +59,9 @@ if you don't enable login.
### Startup options
* Run without database, check [.env.no-db](https://github.com/sqlchat/sqlchat/blob/main/.env.no-db).
* Run without database, check [.env.nodb](https://github.com/sqlchat/sqlchat/blob/main/.env.nodb).
This is suitable if you just want to use for yourself.
* Run with database, check [.env.use-db](https://github.com/sqlchat/sqlchat/blob/main/.env.use-db).
* Run with database, check [.env.usedb](https://github.com/sqlchat/sqlchat/blob/main/.env.usedb).
This is suitable if you want to run a similar multi-tenant service as [sqlchat.ai](https://sqlchat.ai) where you need manage account, usage and etc.
#### OpenAI related
@ -99,7 +99,7 @@ This is suitable if you want to run a similar multi-tenant service as [sqlchat.a
1. Make a copy of the example environment variables file:
```bash
cp .env.use-db .env
cp .env.usedb .env
```
1. Add your [API key](https://platform.openai.com/account/api-keys) and OpenAI API Endpoint(optional) to the newly created `.env` file.

View File

@ -79,7 +79,7 @@ docker run --name sqlchat --platform linux/amd64 --env NEXTAUTH_SECRET=xxx --env
1. 复制示例环境变量文件;
```bash
cp .env.use-db .env
cp .env.usedb .env
```
1. 生成 `prisma` 客户端

View File

@ -3,8 +3,8 @@
"private": false,
"scripts": {
"dev": "next dev",
"no-db": "env-cmd -f .env.no-db pnpm dev",
"use-db": "env-cmd -f .env.use-db pnpm dev",
"nodb": "env-cmd -f .env.nodb pnpm dev",
"usedb": "env-cmd -f .env.usedb pnpm dev",
"build": "prisma generate && next build",
"build-prisma-deploy": "prisma generate && next build && prisma migrate deploy",
"export": "next export",