Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

📝 docs: add notes #3039

Merged
merged 1 commit into from
Jun 25, 2024
Merged

📝 docs: add notes #3039

merged 1 commit into from
Jun 25, 2024

Conversation

Zach677
Copy link
Contributor

@Zach677 Zach677 commented Jun 25, 2024

💻 变更类型 | Change Type

  • ✨ feat
  • 🐛 fix
  • ♻️ refactor
  • 💄 style
  • 🔨 chore
  • ⚡️ perf
  • 📝 docs

🔀 变更说明 | Description of Change

📝 补充信息 | Additional Information

Copy link

vercel bot commented Jun 25, 2024

@Ssttar is attempting to deploy a commit to the LobeHub Pro Team on Vercel.

A member of the Team first needs to authorize it.

@lobehubbot
Copy link
Member

👍 @Ssttar

Thank you for raising your pull request and contributing to our Community
Please make sure you have followed our contributing guidelines. We will review it as soon as possible.
If you encounter any problems, please feel free to connect with us.
非常感谢您提出拉取请求并为我们的社区做出贡献,请确保您已经遵循了我们的贡献指南,我们会尽快审查它。
如果您遇到任何问题,请随时与我们联系。

Copy link

codecov bot commented Jun 25, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.41%. Comparing base (8e54ca0) to head (72c02e4).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3039   +/-   ##
=======================================
  Coverage   93.41%   93.41%           
=======================================
  Files         381      381           
  Lines       23525    23525           
  Branches     1699     1798   +99     
=======================================
  Hits        21977    21977           
  Misses       1548     1548           
Flag Coverage Δ
app 93.41% <ø> (ø)
server 68.73% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@arvinxx
Copy link
Contributor

arvinxx commented Jun 25, 2024

Thanks~

@arvinxx arvinxx merged commit 23f3efb into lobehub:main Jun 25, 2024
5 of 7 checks passed
@lobehubbot
Copy link
Member

❤️ Great PR @Ssttar ❤️

The growth of project is inseparable from user feedback and contribution, thanks for your contribution! If you are interesting with the lobehub developer community, please join our discord and then dm @arvinxx or @canisminor1990. They will invite you to our private developer channel. We are talking about the lobe-chat development or sharing ai newsletter around the world.
项目的成长离不开用户反馈和贡献,感谢您的贡献! 如果您对 LobeHub 开发者社区感兴趣,请加入我们的 discord,然后私信 @arvinxx@canisminor1990。他们会邀请您加入我们的私密开发者频道。我们将会讨论关于 Lobe Chat 的开发,分享和讨论全球范围内的 AI 消息。

@RubuJam
Copy link
Contributor

RubuJam commented Jun 25, 2024

这里更精确的表达是

应该使用获取API Key所在界面中,CloudFlare提供的API地址,而非`存储桶详细信息`里的`S3 API`地址,后者提供的地址中存在路径信息(即存储桶名),应去除该路径

@lobehubbot
Copy link
Member

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿


The more precise expression here is

The API address provided by CloudFlare in the interface where the API Key is obtained should be used instead of the `S3 API` address in `Bucket Details`. The address provided by the latter contains path information (i.e. bucket name) and should be removed. path

@lobehubbot
Copy link
Member

🎉 This PR is included in version 1.1.12 🎉

The release is available on:

Your semantic-release bot 📦🚀

@Zach677 Zach677 deleted the database/url branch June 28, 2024 05:49
Mingholy pushed a commit to Mingholy/lobe-chat that referenced this pull request Jul 1, 2024
ipoly pushed a commit to ipoly/lobe-chat that referenced this pull request Jul 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants