Re: CS-Studio Phoebus Deployment-Only Version

["Blomley, Edmund \(IBPT\) via Tech-talk" <tech-talk@aps.anl.gov>]

Hey,

what exactly should be part of a possible stripped down version?

https://github.com/ControlSystemStudio/phoebus/blob/master/phoebus-product/pom.xml

- core-launcher

- core-pv-* (depending which one(s) is needed)

- app-display-runtime

- app-display-fonts

- app-display-linearmeter

- app-display-thumbwheel

What about trend/databrowsers? Alarms? Logbooks? …?

We do build a modified version, but I never tried to remove some of the "core" parts such as the editor. I would assume that you would end up with navigation and menu entries which either do nothing or trigger error messages, but for the first iteration that would probably be fine?

Eddy

Am 08.08.2025 um 01:34 schrieb Ramirez-Morales, Jacob J (CONTR) via Tech-talk <tech-talk@aps.anl.gov>:

Hello all,

 

I’m exploring options for deploying CS-Studio Phoebus in an operational environment where it will be used solely by operators. The goal is to have a streamlined version without any developer-focused tools or menus; essentially, an environment where only the windows and panels that were intended to be configured are the only ones accessible to end-users.

 

1. Is there a deployment-oriented build that already exists and is readily available? Or if there are recommended configuration profiles through a “settings.ini” to achieve this?
2. Does anyone have experience or know how to create a “locked-down” Phoebus distribution for operations?

 

Any suggestions, documentation pointers, or examples from existing facilities would be greatly appreciated.

 

Thank you in advance for your insights.

 

Best,

Jacob R.

Attachment: smime.p7s
Description: S/MIME cryptographic signature