Skip to content

Conversation

Haimantika
Copy link
Member

This pull request updates the naming and usage of the DigitalOcean AI inference API key throughout the codebase and documentation to use GRADIENT_AI_INFERENCE_KEY instead of the previous DO_INFERENCE_API_KEY. It also standardizes references to the service as "DigitalOcean Gradient™ AI Serverless Inference API" for clarity and branding consistency. These changes affect environment variable names, deployment templates, configuration files, scripts, and documentation.

Environment variable and configuration updates:

  • Renamed all instances of DO_INFERENCE_API_KEY to GRADIENT_AI_INFERENCE_KEY in environment files (application/env-example), deployment templates (.do/app.template.yaml, .do/deploy.template.yaml), and server configuration (application/src/settings.ts). [1] [2] [3] [4] [5]

  • Updated usage of the API key in code to reference GRADIENT_AI_INFERENCE_KEY, including error messages and required config in generate-invoice.js and invoiceService.ts. [1] [2] [3]

Documentation and branding updates:

  • Standardized all documentation and README references to "DigitalOcean Gradient™ AI Serverless Inference API" and updated instructions to use the new environment variable name. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11]

… AI integration

- Changed environment variable from DO_INFERENCE_API_KEY to GRADIENT_AI_INFERENCE_KEY across configuration files and scripts.
- Updated related comments and error messages to reflect the new variable name for clarity and consistency.
… and configuration

- Changed all instances of "DigitalOcean GradientAI" to "DigitalOcean Gradient™ AI" for branding consistency.
- Updated environment variable names in configuration files and documentation to reflect the new naming convention.
- Ensured clarity in error messages and setup instructions related to the AI service integration.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant