Right now we have a shared haven-dev environment and folder at the beamline in the service account's home folder. This means we have to coordinate to use this environment. A better way is to do development using individual user XRAY accounts. This can be done with a dedicated conda/mamba environment.
[ ] Create a new environment (e.g. haven-25idc)
[ ] Copy (or symlink) a valid configuration file for the beamline (e.g. cp /home/beams/S25IDCUSER/bluesky/iconfig.toml ~/.config/bluesky/iconfig-25idc.toml)
[ ] Include the new config file as an environmental variable (e.g. conda env config vars set HAVEN_CONFIG_FILES=$HOME/.config/bluesky/iconfig-25idc.toml)
Now when you activate that environment, it will use the correct configuration file. N.B. you should do this from the beamline computer, otherwise those devices will not be reachable.
Right now we have a shared haven-dev environment and folder at the beamline in the service account's home folder. This means we have to coordinate to use this environment. A better way is to do development using individual user XRAY accounts. This can be done with a dedicated conda/mamba environment.
cp /home/beams/S25IDCUSER/bluesky/iconfig.toml ~/.config/bluesky/iconfig-25idc.toml)conda env config vars set HAVEN_CONFIG_FILES=$HOME/.config/bluesky/iconfig-25idc.toml)Now when you activate that environment, it will use the correct configuration file. N.B. you should do this from the beamline computer, otherwise those devices will not be reachable.