Re: CS-Studio Phoebus Deployment-Only Version

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

Hey Jacob,

 

I ran some tests with the list I suggested below and it actually works much better than what I would have assumed!

 

All the modules I excluded are actually also not showing up in either the top menu nor any context entries. So, the application framework seems very well done even for this “unintended” usage.

 

There are still a couple of things which you probably do not want to have. Just to give two examples (there are some more):

 

- You are still able to “open files” via the top menu

- You are able to open the “Utility -> OPI converter”

 

The OPI converter is probably an example where the feature was just not put into a “separate” module as the other modules and should probably not too difficult to adjust.

 

The general option to open files (or maybe the whole menu should be “gone): Not sure about that! I would assume for your scenario you only want to have “navigation” via panel buttons.

 

I would suggest that you open an issue on Github: https://github.com/ControlSystemStudio/phoebus/issues

There I can detail my initial findings with screenshots and explanations.

 

Having a default launch panel is trivial via a memento file and some ini configuration to define the memento folder to a write-protected folder.

 

Cheers

eddy

 

 

Von: Ramirez-Morales, Jacob J (CONTR) <RAMIREJJ@nv.doe.gov>
Gesendet: Dienstag, 12. August 2025 19:20
An: Blomley, Edmund (IBPT) <edmund.blomley@kit.edu>; tech-talk@aps.anl.gov
Betreff: RE: [EXTERNAL]Re: CS-Studio Phoebus Deployment-Only Version

 

Hi Eddy,

 

Thanks for the info and link to the pom.xml. My goal is to deploy Phoebus as a runtime-only operator interface – so no editor, no development tools, just the Display Builder runtime and a few essential apps.

 

Essentially, I want to launch straight into our main “.bob” display in fullscreen, and have no way for an operator to switch into edit mode or access unused apps.

 

If this means modifying the pheobus-product/pom.xml and building a stripped version from source, I’m open to that – even if some unused menu entries remain at first.

 

My vision is to have operators with minimal access to edit the screens and simply operate, and have another “version” of Phoebus where the the SME or Controls Engineer comes in with full access to CSS tools.

 

Does that sound like the right subset to start with?

 

Best,

Jacob R.

 

From: Blomley, Edmund (IBPT) <edmund.blomley@kit.edu>
Sent: Sunday, August 10, 2025 10:45 PM
To: tech-talk@aps.anl.gov
Cc: Ramirez-Morales, Jacob J (CONTR) <RAMIREJJ@nv.doe.gov>
Subject: [EXTERNAL]Re: CS-Studio Phoebus Deployment-Only Version

 

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