Skip to content

Commit

Permalink
Merge pull request #1 from Dogtiti/main
Browse files Browse the repository at this point in the history
hi
  • Loading branch information
Isratja45 authored Nov 28, 2023
2 parents 253d655 + 4a72b5c commit 4676cd0
Show file tree
Hide file tree
Showing 57 changed files with 5,378 additions and 3,628 deletions.
20 changes: 16 additions & 4 deletions .env.example
Original file line number Diff line number Diff line change
Expand Up @@ -3,15 +3,27 @@ NODE_ENV=development

# Next Auth config:
# Generate a secret with `openssl rand -base64 32`, or visit https://generate-secret.vercel.app/
NEXTAUTH_SECRET=changeme
NEXTAUTH_SECRET=***
NEXTAUTH_URL=http://localhost:3000

# Prisma
DATABASE_URL=file:./db.sqlite

# External APIs:
OPENAI_API_KEY=changeme
OPENAI_API_KEY=***

# Guest Mode:
//The key NEXT_PUBLIC_GUEST_KEY should be in this format: abc,qwe,123, where each comma-separated value can be used
NEXT_PUBLIC_GUEST_KEY=changeme
The key NEXT_PUBLIC_GUEST_KEY should be in this format: abc,qwe,123, where each comma-separated value can be used
NEXT_PUBLIC_GUEST_KEY=***

# Websearch. Fill both of these values to enable it locally
NEXT_PUBLIC_WEB_SEARCH_ENABLED=false # Disables the ability to toggle web search
SERP_API_KEY=*** # https://serper.dev/ for an API key

# Auth providers. Required to enable sign in, in production. Development mode uses local auth.
GOOGLE_CLIENT_ID=***
GOOGLE_CLIENT_SECRET=***
GITHUB_CLIENT_ID=***
GITHUB_CLIENT_SECRET=***
DISCORD_CLIENT_SECRET=***
DISCORD_CLIENT_ID=***
55 changes: 0 additions & 55 deletions .github/ISSUE_TEMPLATE/bug-report---bug反馈.md

This file was deleted.

99 changes: 99 additions & 0 deletions .github/ISSUE_TEMPLATE/bug_report.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,99 @@
name: Bug Report/Bug反馈
description: File a bug report/提交错误报告
labels: ["bug", "needs triage/需要分类"]
body:
- type: markdown
attributes:
value: |
## Before you start/开始之前
Please **make sure you are on the latest version**
请**确保你是最新版本**
If you encountered the issue after you installed, updated, or reloaded, **please try restarting before reporting the bug**.
如果您在安装、更新或重新加载后遇到问题,**请在报告错误之前尝试重新启动**。
- type: checkboxes
id: no-duplicate-issues
attributes:
label: |
Please check that this issue hasn't been reported before
请检查之前没有报告过此问题
description: |
The **Label filters** may help make your search more focussed.
**标签过滤器** 可能有助于使您的搜索更加集中。
options:
- label: "I searched previous [Bug Reports](https://github.com/Dogtiti/AutoGPT-Next-Web/issues?q=is%3Aissue+is%3Aopen+label%3Abug) didn't find any similar reports.我搜索了以前的 [Bug Reports](https://github.com/Dogtiti/AutoGPT-Next-Web/issues?q=is%3Aissue+is%3Aopen+label%3Abug) 没有找到任何类似的报告。"
required: true
- type: textarea
id: expected
attributes:
label: Expected Behavior/预期行为
description: Tell us what **should** happen.告诉我们**应该**发生什么
validations:
required: true
- type: textarea
id: what-happened
attributes:
label: Current behaviour/当前行为
description: |
Tell us what happens instead of the expected behavior.
告诉我们发生了什么而不是预期的行为
Adding of screenshots really helps.
添加屏幕截图确实有帮助
validations:
required: true
- type: textarea
id: reproduce
attributes:
label: Steps to reproduce/重现步骤
description: |
Which exact steps can a developer take to reproduce the issue?
开发人员可以采取哪些具体步骤来重现该问题?
The more detail you provide, the easier it will be to narrow down and fix the bug.
您提供的细节越多,缩小和修复错误的范围就越容易
Please paste in tasks and/or queries **as text, not screenshots**.
请粘贴任务和/或查询**作为文本,而不是屏幕截图**
placeholder: |
Example of the level of detail needed to reproduce any bugs efficiently and reliably.
高效可靠地重现任何错误所需的详细程度示例。
1. Go to the '...' page.
转到“...”页面。
2. Click on the '...' button.
单击“...”按钮。
3. Scroll down to '...'.
向下滚动到“...”。
4. Observe the error.
观察错误
validations:
required: true
- type: textarea
id: possible-solution
attributes:
label: Possible solution/可能的解决方案
placeholder: I think that change foo to type bar would fix it.../我认为将 foo 更改为 bar 类型会解决它
description: |
Not obligatory, but please suggest a fix or reason for the bug, if you have an idea.
不是强制性的,但如果您有想法,请提出错误的修复或原因。
- type: checkboxes
id: operating-systems
attributes:
label: Which Operating Systems are you using?您使用的是哪种操作系统?
description: You may select more than one.您可以选择多个。
options:
- label: Android
- label: iPhone/iPad
- label: Linux
- label: macOS
- label: Windows
- type: checkboxes
id: acknowledgements
attributes:
label: 'Acknowledgements致谢'
description: 'Please confirm the following:请确认以下内容'
options:
- label: 'My issue title is concise, descriptive, and in title casing.我的问题标题简明扼要,具有描述性,并且使用标题框'
required: true
- label: 'I have searched the existing issues to make sure this bug has not been reported yet.我已经搜索了现有问题以确保尚未报告此错误。'
required: true
- label: 'I am using the latest version of AutoGPT-Next-Web.我使用的是最新版本的 AutoGPT-Next-Web'
required: true
- label: 'I have provided enough information for the maintainers to reproduce and diagnose the issue.我已经为维护者提供了足够的信息来重现和诊断问题。'
required: true

This file was deleted.

27 changes: 0 additions & 27 deletions .github/ISSUE_TEMPLATE/feature-request---功能要求.md

This file was deleted.

61 changes: 61 additions & 0 deletions .github/ISSUE_TEMPLATE/feature-request.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,61 @@
name: Feature Request / Enhancement 功能请求/增强
description: Suggest a new feature or feature enhancement for the project 为项目提出新功能或功能增强建议
labels: ["enhancement", "needs triage"]
body:
- type: checkboxes
id: no-duplicate-issues
attributes:
label: "⚠️ Please check that this feature request hasn't been suggested before.请检查之前是否没有建议过此功能请求。"
description: "The **Label filters** may help make your search more focussed.标签过滤器可能有助于使您的搜索更加集中。"
options:
- label: "I searched previous [Ideas in issue](https://github.com/Dogtiti/AutoGPT-Next-Web/issues) didn't find any similar feature requests.我搜索了之前的 [Ideas in issue](https://github.com/Dogtiti/AutoGPT-Next-Web/issues) 没有找到任何类似的功能请求。"
required: true

- type: textarea
id: feature-description
validations:
required: true
attributes:
label: "🔖 Feature description 功能说明"
description: "A clear and concise description of what the feature request is.对功能请求是什么的清晰简洁的描述。"
placeholder: "You should add ...你应该添加..."

- type: textarea
id: solution
validations:
required: true
attributes:
label: "✔️ Solution 解决方案"
description: "A clear and concise description of what you want to happen, and why.清晰简洁地描述您想要发生的事情以及原因。"
placeholder: "In my use-case, ...在我的用例中,..."

- type: textarea
id: alternatives
validations:
required: false
attributes:
label: "❓ Alternatives 备选方案"
description: "A clear and concise description of any alternative solutions or features you've considered.对您考虑过的任何替代解决方案或功能的清晰简洁的描述"
placeholder: "I have considered ...我考虑过..."

- type: textarea
id: additional-context
validations:
required: false
attributes:
label: "📝 Additional Context 附加上下文"
description: "Add any other context or screenshots about the feature request here.在此处添加有关功能请求的任何其他上下文或屏幕截图。"
placeholder: "..."

- type: checkboxes
id: acknowledgements
attributes:
label: 'Acknowledgements 致谢'
description: 'Please confirm the following:请确认以下内容:'
options:
- label: 'My issue title is concise, descriptive, and in title casing.我的问题标题简明扼要,具有描述性,并且使用标题框。'
required: true
- label: 'I have searched the existing issues to make sure this feature has not been requested yet.我已经搜索了现有问题以确保尚未请求此功能。'
required: true
- label: 'I have provided enough information for the maintainers to understand and evaluate this request.我已经为维护者提供了足够的信息来理解和评估这个请求。'
required: true
55 changes: 55 additions & 0 deletions .github/workflows/build-docker-image.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,55 @@
name: Build and publish the Docker image

on:
workflow_dispatch:
release:
types: [published]

env:
REGISTRY: docker.io
IMAGE_NAME: dogtititi/autogpt-next-web

jobs:
build-and-push-image:
runs-on: ubuntu-latest
permissions:
contents: read
packages: write

steps:
- name: Checkout repository
uses: actions/checkout@v3
- name: Log in to the Container registry
if: github.event_name != 'pull_request'
uses: docker/login-action@v2
with:
registry: ${{ env.REGISTRY }}
username: ${{ secrets.DOCKER_USERNAME }}
password: ${{ secrets.DOCKER_TOKEN }}
- name: Extract metadata (tags, labels) for Docker
id: meta
uses: docker/metadata-action@v4
with:
images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}

- name: Build and push Docker image
uses: docker/build-push-action@v4
with:
context: .
file: prod.Dockerfile
build-args: |
NEXTAUTH_URL=http://localhost:3000
DATABASE_URL=file:./db.sqlite
OPENAI_API_KEY: ${OPENAI_API_KEY}
NEXT_PUBLIC_WEB_SEARCH_ENABLED: ${NEXT_PUBLIC_WEB_SEARCH_ENABLED}
SERP_API_KEY: ${SERP_API_KEY}
NEXT_PUBLIC_FF_AUTH_ENABLED: ${NEXT_PUBLIC_FF_AUTH_ENABLED}
GOOGLE_CLIENT_ID: ${GOOGLE_CLIENT_ID}
GOOGLE_CLIENT_SECRET: ${GOOGLE_CLIENT_SECRET}
GITHUB_CLIENT_ID: ${GITHUB_CLIENT_ID}
GITHUB_CLIENT_SECRET: ${GITHUB_CLIENT_SECRET}
DISCORD_CLIENT_ID: ${DISCORD_CLIENT_ID}
DISCORD_CLIENT_SECRET: ${DISCORD_CLIENT_SECRET}
push: true
tags: ${{ steps.meta.outputs.tags }}
labels: ${{ steps.meta.outputs.labels }}
40 changes: 40 additions & 0 deletions .github/workflows/sync-fork.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,40 @@
name: Sync Fork

permissions:
contents: write

on:
schedule:
- cron: "0 0 * * *" # every
workflow_dispatch:

jobs:
sync_fork:
name: Sync latest commits from upstream repo
runs-on: ubuntu-latest
if: ${{ github.event.repository.fork }}

steps:
# Step 1: run a standard checkout action
- name: Checkout target repo
uses: actions/checkout@v3

# Step 2: run the sync action
- name: Sync upstream changes
id: sync
uses: aormsby/[email protected]
with:
upstream_sync_repo: Dogtiti/AutoGPT-Next-Web
upstream_sync_branch: main
target_sync_branch: main
target_repo_token: ${{ secrets.GITHUB_TOKEN }} # automatically generated, no need to set

# Set test_mode true to run tests instead of the true action!!
test_mode: false

- name: Sync check
if: failure()
run: |
echo "::Error :权限不足,请前往仓库首页手动执行[Sync fork]。"
echo "::Error :Due to insufficient permissions,Please go to the repository homepage and manually perform [Sync fork]."
exit 1
Loading

0 comments on commit 4676cd0

Please sign in to comment.