Restart troubleshooting documentation. #5317
Conversation
| But clicking "Resume" still starts a fresh new chat. | ||
|
|
||
| **Details** | ||
| **Description** |
There was a problem hiding this comment.
Kept this Sessions are not restored here. But I feel like troubleshooting is not a good place for it.
Is there a better place to move it to?
There was a problem hiding this comment.
IIRC Robert was suggesting an Advanced Configuration section, and linked from the main README. That could work?
There was a problem hiding this comment.
Alright. Yeah just remembered the thread. I'll take a stab at it.
|
|
||
| ## How to Persist Session Data | ||
|
|
||
| ### Development Workflow |
There was a problem hiding this comment.
I got this to work with the below instructions but could not get it to work using the docker command. I ran the docker command with:
-e FILE_STORE="local" -e FILE_STORE_DATA="<path>" -e JWT_SECRET="secretpass"
What am I missing?
There was a problem hiding this comment.
-e FILE_STORE="local" -e FILE_STORE_DATA="" -e JWT_SECRET="secretpass"
Isn't it FILE_STORE_DATA -> FILE_STORE_PATH instead?
| @@ -63,6 +63,9 @@ run OpenHands in a scriptable [headless mode](https://docs.all-hands.dev/modules | |||
| interact with it via a [friendly CLI](https://docs.all-hands.dev/modules/usage/how-to/cli-mode), | |||
| or run it on tagged issues with [a github action](https://github.com/All-Hands-AI/OpenHands/blob/main/openhands/resolver/README.md). | |||
|
|
|||
| Follow the [Persisting Session Data](https://docs.all-hands.dev/modules/usage/how-to/persist-session-data) guide if you | |||
| would like your session data to persist. | |||
There was a problem hiding this comment.
End-user friendly description of the problem this fixes or functionality that this introduces
Restart troubleshooting documentation.
Give a summary of what the PR does, explaining any non-trivial design decisions
Restarting this documentation with up to date information. Will try to fill this up appropriately. Ideally it should not be filled with bugs that can be resolved through code.
Link of any specific issues this addresses
To run this PR locally, use the following command: