Welcome to the official documentation repository for Cloud Temple. Here, you’ll find guides and resources to help you better understand and utilize Cloud Temple’s services and solutions.
A PROD version of this documentation is available here. This repository and the website are synchronized to ensure up-to-date content.
A DEV version of this documentation is available here.
This project is continuously updated with new guides and improvements.
We value your contributions! Whether it’s improving an existing guide or creating a new one, your input helps us make this repository better.
- Fork this repository: Clone your fork to your local environment.
- Make your changes: Update or create guides.
- Submit a Pull Request (PR): Propose your changes to the develop branch.
Our team will review your contribution, provide feedback if needed, and integrate approved changes.
• Ensure your contributions are accurate, tested, and well-documented. • Include a brief explanation of your changes in the PR comments. • Follow the structure and style of existing guides for consistency.
By contributing to this repository, you agree to the terms outlined in the LICENSE file.
To get started, follow these simple steps:
- Navigate to the Docker directory:
cd docker/local- Launch the services with Docker Compose:
docker-compose up- Access the documentation locally:
Open your browser and go to: http://localhost:3000/docs/
Base url is set to "/docs" when running on non production build (locally or deployed on github pages)
🎉 Your local environment is ready!
- Node.js (version 18.0 or higher)
- yarn package manager
-
Install dependencies
yarn install
-
Start the development server
yarn start
This command will start the Docusaurus development server with hot reloading enabled.
-
Access the documentation locally
Open your browser and go to: http://localhost:3000/docs/
Base url is set to "/docs" when running on non production build (locally or deployed on github pages)
The documentation supports 5 languages: French (default), English, Spanish, Italian, and German.
-
Default Language (French)
- All content is written in French in the
/docs/directory - This is the source language for all translations
- All content is written in French in the
-
Start with a specific language
# Start in English yarn start --locale en # Start in Spanish yarn start --locale es # Start in Italian yarn start --locale it # Start in German yarn start --locale de
🎉 Your local environment is ready!
To get started, follow these simple steps:
- Build the docker image:
docker build -t docs:v3 . -f docker/production/Dockerfile- Launch the services with Docker Compose:
docker run -it --rm -p 8080:80 --name docs docs:v3- Access the documentation locally (all pages and all langages should work):
Open your browser and go to: http://localhost:8080
Base url is set to "/" on production build
The production image (nginx:stable-alpine stage) embeds the following OCI standard labels:
| Label | Value |
|---|---|
org.opencontainers.image.title |
Cloud Temple Documentation |
org.opencontainers.image.description |
Cloud Temple official documentation site (Docusaurus static build served by nginx) |
org.opencontainers.image.vendor |
Cloud Temple |
org.opencontainers.image.source |
https://github.com/Cloud-Temple/docs |
org.opencontainers.image.licenses |
proprietary |
You can inspect the labels of a built image with:
docker inspect docs:v3 --format '{{ json .Config.Labels }}' | jqSecurity note: Alpine packages in the final stage are upgraded at build time (
apk upgrade --no-cache) to ensure all OS-level CVEs are patched. Rebuild the image regularly to pick up new security fixes.
This project includes several scripts to automate documentation and translation tasks. For complete technical details on all scripts, please refer to the Scripts README.
docs/llmaas/models.md is a selection guide. It links to the maintained catalogue instead of duplicating model counts, performance tables and lifecycle dates.
| Information | Maintained source |
|---|---|
| Published lifecycle, LTS, retirement dates and migration targets | LLMaaS lifecycle (status/web/src/data/lifecycle.ts) |
| Product announcements | LLMaaS changelog (status/web/src/data/changelog.ts) |
| Model descriptions and capabilities | LLMaaS repository: scripts/models_information/models_config.yaml |
| Identifiers exposed by the service | Authenticated GET /v1/models |
| Availability and observed performance | LLMaaS status |
The published lifecycle is authoritative for lifecycle dates, LTS status and migration targets. If model inventories or historical copies disagree, reconcile their lifecycle fields with this source; do not copy conflicting dates into these docs. Technical capabilities must be checked against the effective service configuration and exposed API metadata.
For each model release, update the model metadata and published lifecycle in their owning repositories together. Check agreement on identifiers, support dates and migration targets before release. Update this documentation only when usage changes (API contract, capability, integration or migration procedure), then regenerate translations and build the site.
Keep example model IDs in configuration where practical; validate them against the API and lifecycle when changing a guide. Do not recreate exhaustive model lists in the overview, FAQ or concepts pages.
The former memory-bank/models_config.yaml is a historical copy, not a current catalogue. yarn generate:models / yarn generate:docs and the old Python entry point now exit with an explanatory error, without overwriting the selection guide.
The documentation supports 5 languages: French (source), English, German, Spanish, and Italian. The French content in /docs/ is the source — translations are generated automatically via the Cloud Temple LLMaaS API, with SHA-256 change detection so only modified files are re-translated. The API token is passed via the --token CLI flag (recommended) or environment variables.
⚠️ Never edit files ini18n/manually — they are overwritten on each translation run. Always edit the French source in/docs/.
➡️ Full setup (venv, install, token, usage, rules and troubleshooting): see the Scripts Documentation.
For a complete list of commands, advanced features, and troubleshooting, please see the detailed Scripts Documentation.