選択できるのは25トピックまでです。 トピックは、先頭が英数字で、英数字とダッシュ('-')を使用した35文字以内のものにしてください。
-LAN- ce774c6d15 release(update): bump version to 0.10.0-beta2 1年前
..
.husky feat: add format util unit and add pre-commit unit check (#8427) 1年前
.vscode feat: add frontend unit test framework (#6426) 1年前
app Merge branch 'feat/attachments' into release/0.10.0-beta1 1年前
assets fix: missing files (#2291) 1年前
bin Feat/embedding (#553) 2年前
config feat: allow users to specify timeout for text generations and workflows by environment variable (#8395) 1年前
context chore: merge main 1年前
docker feat: allow users to specify timeout for text generations and workflows by environment variable (#8395) 1年前
hooks feat: regenerate in `Chat`, `agent` and `Chatflow` app (#7661) 1年前
i18n chore: merge main 1年前
models chore: merge main 1年前
public fix: embedded chat on ios (#8718) 1年前
service Merge branch 'feat/attachments' into release/0.10.0-beta1 1年前
themes merge main 1年前
types webapp chat embedded chat 1年前
utils text-generation support file type 1年前
.dockerignore build: fix .dockerignore file (#800) 2年前
.editorconfig Initial commit 2年前
.env.example feat: allow users to specify timeout for text generations and workflows by environment variable (#8395) 1年前
.eslintignore feat: add code style (#242) 2年前
.eslintrc.json Feat/i18n restructure (#2529) 1年前
.gitignore feat: support assistant frontend (#2139) 1年前
Dockerfile feat: Support NEXT_TELEMETRY_DISABLED (#7181) 1年前
README.md feat: add format util unit and add pre-commit unit check (#8427) 1年前
global.d.ts feat: support assistant frontend (#2139) 1年前
jest.config.ts feat: add frontend unit test framework (#6426) 1年前
next.config.js feat:add tts-streaming config and future (#5492) 1年前
package.json release(update): bump version to 0.10.0-beta2 1年前
postcss.config.js Initial commit 2年前
tailwind.config.js agent tool in chat 1年前
tsconfig.json Initial commit 2年前
typography.js Initial commit 2年前
yarn.lock fix: file extension 1年前

README.md

Dify Frontend

This is a Next.js project bootstrapped with create-next-app.

Getting Started

Run by source code

To start the web frontend service, you will need Node.js v18.x (LTS) and NPM version 8.x.x or Yarn.

First, install the dependencies:

npm install
# or
yarn install --frozen-lockfile

Then, configure the environment variables. Create a file named .env.local in the current directory and copy the contents from .env.example. Modify the values of these environment variables according to your requirements:

cp .env.example .env.local
# For production release, change this to PRODUCTION
NEXT_PUBLIC_DEPLOY_ENV=DEVELOPMENT
# The deployment edition, SELF_HOSTED
NEXT_PUBLIC_EDITION=SELF_HOSTED
# The base URL of console application, refers to the Console base URL of WEB service if console domain is
# different from api or web app domain.
# example: http://cloud.dify.ai/console/api
NEXT_PUBLIC_API_PREFIX=http://localhost:5001/console/api
# The URL for Web APP, refers to the Web App base URL of WEB service if web app domain is different from
# console or api domain.
# example: http://udify.app/api
NEXT_PUBLIC_PUBLIC_API_PREFIX=http://localhost:5001/api

# SENTRY
NEXT_PUBLIC_SENTRY_DSN=

Finally, run the development server:

npm run dev
# or
yarn dev

Open http://localhost:3000 with your browser to see the result.

You can start editing the file under folder app. The page auto-updates as you edit the file.

Deploy

Deploy on server

First, build the app for production:

npm run build

Then, start the server:

npm run start

If you want to customize the host and port:

npm run start --port=3001 --host=0.0.0.0

Lint Code

If your IDE is VSCode, rename web/.vscode/settings.example.json to web/.vscode/settings.json for lint code setting.

Test

We start to use Jest and React Testing Library for Unit Testing.

You can create a test file with a suffix of .spec beside the file that to be tested. For example, if you want to test a file named util.ts. The test file name should be util.spec.ts.

Run test:

npm run test

If you are not familiar with writing tests, here is some code to refer to:

Documentation

Visit https://docs.dify.ai/getting-started/readme to view the full documentation.

Community

The Dify community can be found on Discord community, where you can ask questions, voice ideas, and share your projects.