Skip to content

Commit 087e964

Browse files
committed
guides: deploy: mention the need to specify stdcm search env
And specify how to do so Signed-off-by: Baptiste Prevot <[email protected]>
1 parent 6fdf3f9 commit 087e964

File tree

4 files changed

+70
-2
lines changed

4 files changed

+70
-2
lines changed

content/docs/guides/deploy/_index.en.md

+7-1
Original file line numberDiff line numberDiff line change
@@ -12,4 +12,10 @@ We will cover how to deploy OSRD within the following setups:
1212
- [Using docker compose]({{< ref "/docs/guides/deploy/docker-compose" >}}) on a single node.
1313
- [Using helm]({{< ref "/docs/guides/deploy/docker-compose" >}}) on a kubernetes cluster.
1414

15-
It is also possible to deploy each service of OSRD manually on a system, but we will not cover this topic within this guide.
15+
It is also possible to deploy each service of OSRD manually on a system, but we will not cover this topic within this guide.
16+
17+
18+
{{% alert title="NB" color="warning" %}}
19+
In order for the STDCM tool to function, you'll need to setup the STDCM Search Environment, a configuration stored in database.
20+
See the [dedicated page]({{< ref "/docs/guides/deploy/stdcm-search-env" >}}) for more information.
21+
{{% /alert %}}

content/docs/guides/deploy/_index.fr.md

+7-1
Original file line numberDiff line numberDiff line change
@@ -12,4 +12,10 @@ Nous allons couvrir comment déployer OSRD dans les configurations suivantes :
1212
- [Utiliser docker compose]({{< ref "/docs/guides/deploy/docker-compose" >}}) sur un seul nœud.
1313
- [Utiliser helm]({{< ref "/docs/guides/deploy/docker-compose" >}}) sur un cluster kubernetes.
1414

15-
Il est également possible de déployer manuellement chaque service d'OSRD sur un système, mais nous ne couvrirons pas ce sujet dans ce guide.
15+
Il est également possible de déployer manuellement chaque service d'OSRD sur un système, mais nous ne couvrirons pas ce sujet dans ce guide.
16+
17+
18+
{{% alert title="NB" color="warning" %}}
19+
Pour que l'outil STDCM fonctionne, il faut configurer l'environnement de recherche STDCM, une configuration stockée en base de données.
20+
Consultez la [page dédiée]({{< ref "/docs/guides/deploy/stdcm-search-env" >}}) pour plus d'informations.
21+
{{% /alert %}}
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
---
2+
title: STDCM search environment configuration
3+
linkTitle: STDCM search environment configuration
4+
weight: 10
5+
description: How to configure the STDCM search environment
6+
---
7+
8+
In order for the STDCM tool to function, you'll need to setup the STDCM Search Environment, a configuration stored in database.
9+
10+
The configurable fields are as such:
11+
```rust
12+
pub struct StdcmSearchEnvironment {
13+
pub infra_id: i64,
14+
pub electrical_profile_set_id: Option<i64>,
15+
pub work_schedule_group_id: Option<i64>,
16+
pub timetable_id: i64,
17+
pub search_window_begin: NaiveDateTime,
18+
pub search_window_end: NaiveDateTime,
19+
}
20+
```
21+
22+
This configuration is queried by the frontend.
23+
That way, the right objects and time bounds are used transparently by the user.
24+
25+
In order to setup this config, you can either
26+
* Use the provided REST API (see [the editoast openAPI]({{< ref "/docs/reference/apis/editoast#operations-tag-stdcm_search_environment" >}})
27+
in the stdcm_search_environment section)
28+
* Use the provided editoast cli (run `editoast stdcm-search-env help` for more information)
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
---
2+
title: "Configuration de l'environnement de recherche STDCM"
3+
linkTitle: "Configuration de l'environnement de recherche STDCM"
4+
weight: 10
5+
description: Comment configurer l'environnement de recherche STDCM
6+
---
7+
8+
Pour que l'outil STDCM fonctionne, il faut configurer l'environnement de recherche STDCM, une configuration stockée en base de données.
9+
10+
Les champs configurables sont les suivants :
11+
```rust
12+
pub struct StdcmSearchEnvironment {
13+
pub infra_id: i64,
14+
pub electrical_profile_set_id: Option<i64>,
15+
pub work_schedule_group_id: Option<i64>,
16+
pub timetable_id: i64,
17+
pub search_window_begin: NaiveDateTime,
18+
pub search_window_end: NaiveDateTime,
19+
}
20+
```
21+
22+
Cette configuration est récupérée par le frontend afin que les bons objets et bornes temporelles soient utilisés
23+
de manière transparente par l'utilisateur.
24+
25+
Pour configurer cette environnement, vous pouvez soit :
26+
* Utiliser l'API REST prévue à cet effet (voir [l'openAPI d'editoast]({{< ref "/docs/reference/apis/editoast#operations-tag-stdcm_search_environment" >}})
27+
dans la section stdcm_search_environment)
28+
* Utiliser le CLI editoast (exécutez `editoast stdcm-search-env help` pour plus d'informations)

0 commit comments

Comments
 (0)