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

Adding Mixtral's Codestral, Added Deployment Guide for Cloudflare Pages #1268

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

BurhanCantCode
Copy link

Changes Made

1. Added Mixtral's Codestral Model

  • Added Codestral to the supported models list
  • Integrated with existing Mixtral provider configuration
  • Updated model selection UI to include the new option

2. Enhanced Deployment Documentation

  • Added detailed Cloudflare Pages deployment guide
  • Included step-by-step instructions for:
    • Setting up Cloudflare account
    • Configuring environment variables
    • Handling API keys securely
    • Troubleshooting common deployment issues

Testing Done

  • Verified Codestral model integration works correctly
  • Tested deployment guide steps on a fresh Cloudflare account
  • Validated environment variable configuration process

Notes for Reviewers

  • Please check if the deployment guide is clear enough for new users
  • Verify if Codestral integration follows our existing provider patterns

- Implement Codestral provider class with Mistral integration
- Configure API endpoints and model parameters
- Add documentation for Codestral usage
- Fix TypeScript type definitions
- Resolve linting and formatting issues
@leex279
Copy link
Collaborator

leex279 commented Feb 9, 2025

Hi @BurhanCantCode,
thanks for the PR.

A few things on this:

  • Split in multiple PRs, cause it should be one specific Feature per PR, so it also can be reflected correctly in the Release Notes later
  • Cloudflare => I dont think thats something for the official docs, cause this needs to be maintained in all coming releases and there are maybe things which change over time. This is not manageable by the core team. I think this is covered quite code by community posts and youtube videos (like one of my videos on this)

@coleam00 => your opinion on these PR(s)?

@leex279 leex279 added the core-team-discussion to be discussed within the core team label Feb 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core-team-discussion to be discussed within the core team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants