doc: mention no-cache mode for editoast and core debugging

Signed-off-by: Pierre-Etienne Bougué <bougue.pe@proton.me>

Author: bougue-pe

core/README.md

@@ -111,6 +111,16 @@ For core:
 ./gradlew shadowJar && ALL_INFRA=true java -jar -ea -Xmx12g -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=dump.hprof build/libs/osrd-all.jar worker --editoast-url http://localhost:8090/
 ```
 
+Removing cache on editoast is also usually helpful to repeat requests
+(please see the [dedicated section](../editoast/README.md#no-cache-mode)). \
+For editoast server, combining single-worker and no-cache modes requires a
+local instance (or a tweak of `docker-compose.single-worker.yml`):
+```sh
+cd ../editoast
+EDITOAST_CORE_SINGLE_WORKER=true NO_CACHE=true cargo run -- runserver
+```
+
+
 Clean or restart the whole stack can be necessary sometimes and is also available
 through docker compose CLI (the following wipes the database too):
 ```sh

editoast/README.md

@@ -77,6 +77,13 @@ cargo install --locked taplo-cli
 
 To setup `grcov`, please see [its documentation](https://github.com/mozilla/grcov#how-to-get-grcov)
 
+## No-cache mode
+
+Running editoast with deactivated cache can help repeating calls when debugging.
+```sh
+NO_CACHE=true cargo run -- runserver
+```
+
 ## For M1 MacOS users
 
 Our `docker-compose.yml` at the root of the project uses the `postgis` image by default.