You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As part of #3 we want to be able to inject from the server to the worker the devices and plans that are allowed. To make sure that we never try to ship a "live" ophyd object between the processes, we should use happi as the device database.
The text was updated successfully, but these errors were encountered:
I assume that this functionality is mostly implemented: the plans and devices are imported from startup scripts or startup modules and permissions may be set to restrict direct access to plans and devices for user that belong to defined user groups. Startup scripts may also call API to load devices from Happi.
As part of #3 we want to be able to inject from the server to the worker the devices and plans that are allowed. To make sure that we never try to ship a "live" ophyd object between the processes, we should use happi as the device database.
The text was updated successfully, but these errors were encountered: