added algolia
# Description
Please include a summary of the changes and the related issue. Please
also include relevant motivation and context.
## Checklist before requesting a review
Please delete options that are not relevant.
- [ ] My code follows the style guidelines of this project
- [ ] I have performed a self-review of my code
- [ ] I have commented hard-to-understand areas
- [ ] I have ideally added tests that prove my fix is effective or that
my feature works
- [ ] New and existing unit tests pass locally with my changes
- [ ] Any dependent changes have been merged
## Screenshots (if appropriate):
# Description
emedding -> embedding
## Checklist before requesting a review
Please delete options that are not relevant.
- [x] My code follows the style guidelines of this project
- [ ] I have performed a self-review of my code
- [x] I have commented hard-to-understand areas
- [ ] I have ideally added tests that prove my fix is effective or that
my feature works
- [ ] New and existing unit tests pass locally with my changes
- [ ] Any dependent changes have been merged
## Screenshots (if appropriate):
added search with lunr
# Description
Please include a summary of the changes and the related issue. Please
also include relevant motivation and context.
## Checklist before requesting a review
Please delete options that are not relevant.
- [ ] My code follows the style guidelines of this project
- [ ] I have performed a self-review of my code
- [ ] I have commented hard-to-understand areas
- [ ] I have ideally added tests that prove my fix is effective or that
my feature works
- [ ] New and existing unit tests pass locally with my changes
- [ ] Any dependent changes have been merged
## Screenshots (if appropriate):
# Description
Please include a summary of the changes and the related issue. Please
also include relevant motivation and context.
## Checklist before requesting a review
Please delete options that are not relevant.
- [ ] My code follows the style guidelines of this project
- [ ] I have performed a self-review of my code
- [ ] I have commented hard-to-understand areas
- [ ] I have ideally added tests that prove my fix is effective or that
my feature works
- [ ] New and existing unit tests pass locally with my changes
- [ ] Any dependent changes have been merged
## Screenshots (if appropriate):
Fixed license link
# Description
Fixed license link in intro
## Checklist before requesting a review
Please delete options that are not relevant.
- [x] My code follows the style guidelines of this project
- [x] I have performed a self-review of my code
- [x] I have commented hard-to-understand areas
- [x] I have ideally added tests that prove my fix is effective or that
my feature works
- [x] New and existing unit tests pass locally with my changes
- [x] Any dependent changes have been merged
By not specifying '-f docker-compose.yml' in the docker compose command, it allows
more flexible use of configuration files. docker-compose.yml is already the default
config file when none is specified, and this also allows overrides via
docker-compose.override.yml, which is recognized by default.
* feat: add user user identity table
* feat: add user openai api key input
* feat: add encryption missing message
* chore: log more details about 422 errors
* docs(API): update api creation path
* feat: use user openai key if defined
* 📝 add BACKEND_URL to documentation
* 📝 add migrations script to get_started doc
* 📝 add BACKEND_URL to documentation
* 📝 add Resend API to documentation
* 🔥 remove broken link in get_started doc
* feat: user can create api keys
* fix: linting on build
* Update backend/routes/api_key_routes.py
* chore: rename and refactor AuthBearer
* chore: add types
* Update intro.md
IMO, Migrations Script sounds like we have a Quivr v1, and there is a new architecture (v2), and we need to run these scripts to "migrate" to the new version.
* Update README.md
Revert change. It's included on intro.md
