Configuration¶
fortranspire reads its configuration exclusively from environment
variables (or from a local .env file, loaded automatically). A complete
template is shipped at the root of the repository as .env.example.
LLM endpoint¶
Variable |
Default |
Description |
|---|---|---|
|
|
Base URL of any OpenAI-compatible chat endpoint |
|
(unset) |
Bearer token sent to the endpoint |
|
|
Model name passed in every request |
|
|
Sampling temperature |
|
|
Nucleus sampling cutoff |
|
|
Maximum tokens per completion |
The same variables work for Mistral La Plateforme, a self-hosted vLLM server, an Ollama instance, or any other OpenAI-compatible backend.
MCP server¶
Variable |
Default |
Description |
|---|---|---|
|
|
Bind address |
|
|
Listen port |
|
(unset) |
If set, require |
request (skipped on |
Pipeline behavior¶
Variable |
Default |
Description |
|---|---|---|
|
repo root |
Where intermediate files are written |
|
|
Maximum LangGraph re-entry count |
|
|
Root for generated Fortran / Cython / JAX |
Compiler toolchain¶
Variable |
Default |
Description |
|---|---|---|
|
|
Compiler used for the CPU syntax checks |
|
|
Compiler used for the OpenACC validation step |
|
|
GPU architecture passed to |
Loading the .env¶
The CLI and the MCP server both call python-dotenv at startup, so simply
placing a .env file at the repository root (or in your working directory)
is enough — no flag required. CI workflows should set the same variables
through repository secrets.