Kyma Companion provides in-app context-sensitive help and general assistance to Kyma users.

• Python 3.12.x
• Poetry
• Redis server

We use Poetry to manage dependencies in the project. Here's a quick guide on how to add, remove, and update dependencies using Poetry.

To install all the dependencies listed in the pyproject.toml file, use the following command:

poetry install

To update a specific dependency to its latest version, use the poetry update command followed by the name of the package:

poetry update {package_name}

To add a new dependency to your project, use the poetry add command followed by the name of the package you want to add:

poetry add {package_name}

Or, with an exact version:

poetry add {package_name}@{version}

To remove a dependency from your project, you can use the poetry remove command followed by the name of the package:

poetry remove {package_name}

To create a virtual environment for the project, navigate to the project's root directory and run the following command:

poetry install

This creates a new virtual environment and installs the project's dependencies.

If you are a PyCharm user and want to use the virtual environment created by Poetry, follow the configuration guides.

Before running the application, you must provide the Redis server. It stores the conversation with a large language model (LLM). Therefore, provide REDIS_URL as an environment variable.

For details on how to create a Redis server, read Create Redis. For example, REDIS_URL="redis://{host or ip}:6379"

You can execute the Kyma Companion locally using the FastAPI framework with the following command:

poetry run fastapi dev src/main.py --port 8000

Or, with a poe task:

poetry run poe run-local

It is recommended to run Kyma Companion with Poetry because it activates and uses its virtual environment if not activated yet.

Alternatively, you can run the application directly using Python and uvicorn instead of FastAPI. To do this, run the following command:

python src/main.py

To enable auto-reloading, pass the --reload argument: bash python src/main.pt --reload For IDEs, such as Pycharm or VS Code, you must pass this argument in the run or debug configuration.

Because the companion uses the FastAPI framework, read the following documentation on how to debug the application with the respective IDE:

• PyCharm
• VS Code

For local development, you can configure LLMs by modifying the config/config.json file. To use a configuration file from a different location, set the CONFIG_PATH environment variable to the path of your desired JSON configuration file.

For tracing, Kyma Companion uses Langfuse. For more information, see Using Langfuse in Kyma Companion.

To execute linting, formatting, and type checking using Ruff, Black, and mypy, respectively use the following command:

poetry run poe codecheck

To fix linting and formatting issues, use the following command:

poetry run poe code-fix

Mypy does not support fixing issues automatically.

It is recommended to execute the Ruff linting check with the poe lint task with the following command:

poetry run poe lint

Alternatively, you can also do it with ruff check directly, where Ruff may have a different version in a different virtual environment.

Linting errors can be fixed with the following command, which applies only the safe fixes by default:

poetry run poe lint-fix

To execute the Black formatting check with the poe format task, use the following command:

poetry run poe format

You can fix formatting erros with the following command:

poetry run poe format-fix

To execute type checking with mypy, use the following command:

poetry run poe typecheck

Mypy does not support fixing issues automatically.

The tests written in the pytest framework can be executed with the following command:

poetry run poe test

Or, with the following command:

poetry run pytest tests

For details about integration tests, read the Integration Tests README file.

For details about blackbox tests, read the Blackbox Tests README file.

Release testing and release creation are two separate processes. For details about release testing, read the Contributor README file.

See the Contributing Rules.

See the Code of Conduct document.

See the license file.