Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update deployment docs based on deploying #842

Merged
merged 2 commits into from
Mar 3, 2025
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 11 additions & 2 deletions docs/how-to/edit-live.md
Original file line number Diff line number Diff line change
Expand Up @@ -54,10 +54,19 @@ The helm chart can be configured to mount a scratch area from the
host machine, include the following in your `values.yaml`:

```yaml
scratch:
hostPath: path/to/scratch/area # e.g. /dls_sw/<my_beamline>/software/blueapi/scratch
scratchHostPath: path/to/scratch/area # e.g. /dls_sw/<my_beamline>/software/blueapi/scratch
```

:::{note}
If you do this then the value of `scratch.root` in your blueapi configuration is no longer particularly important, it only specifies where to mount the scratch area _inside_ the container.
:::

The scratch folder that you're pointing to must exist, not already have a dodal deployment and have correct permissions e.g.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could: It must not already have a deployment of the repo you want in general.


```
cd /dls_sw/<my_beamline>/software/blueapi/
mkdir scratch
chmod o+wrX -R scratch
```

BlueAPI will then checkout the `main` branch of any specified repos into this scratch folder.
Loading