Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| 712:configure_stages [2026/03/05 09:19] – Prinz, Patrick | 712:configure_stages [2026/05/04 12:31] (current) – [Modify secret.properties settings] Veit, Elke | ||
|---|---|---|---|
| Line 529: | Line 529: | ||
| **When using models newer than gpt4o (like gpt5)** | **When using models newer than gpt4o (like gpt5)** | ||
| - | >Most likely the temperature has to be adjusted. Add < | + | >The temperature has to be adjusted |
| - | > | + | >The < |
| **AI content generation feature (OpenAI compatible): | **AI content generation feature (OpenAI compatible): | ||
| Line 625: | Line 625: | ||
| ai.model.url = [azure_ai_ressource_url] | ai.model.url = [azure_ai_ressource_url] | ||
| ai.model.key = [azure_ai_ressource_key] | ai.model.key = [azure_ai_ressource_key] | ||
| - | ai.security.user = [custom_name_to_identify_stages_to_azure] | + | ai.security.user = [arbitrary_custom_name_to_identify_stages_to_azure] |
| ai.translateservice.url = [azure_translate_service_url] | ai.translateservice.url = [azure_translate_service_url] | ||
| Line 693: | Line 693: | ||
| ===== AI Feature Tokenizer Configuration ===== | ===== AI Feature Tokenizer Configuration ===== | ||
| - | LLM that are NOT using the standard byte-pair-encoding algorithm CANNOT be used with the Azure tokenizer. Stages implements the HuggingFaceTokenizer from deep java library to support customized tokenizer. | + | LLM that are NOT using the standard byte-pair-encoding algorithm |
| Add the property “tokenizerFolder” to the cg-host section | Add the property “tokenizerFolder” to the cg-host section | ||