synapps-deploy

Assemble, build, and initialize EPICS synApps support environments for IOC development.

1|1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/BCDA-APS/opencode-skills --skill synapps-deploy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: synapps-deploy
Source: https://github.com/BCDA-APS/opencode-skills/tree/main/synapps-deploy
Command: npx skills add https://github.com/BCDA-APS/opencode-skills --skill synapps-deploy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deploying and building a working EPICS synApps environment is slow and error-prone because it requires correctly selecting module versions, assembling the shared support tree, and creating/adjusting IOC applications from the xxx template.

Core Features & Use Cases

  • Assemble a consistent synApps support tree: Use assemble_synApps to clone modules at tested tags and generate a unified buildable support layout.
  • Customize module selection and versions: Override specific modules, exclude modules, or extend areaDetector submodules using command-line options or a config file.
  • Create and configure new IOCs from the xxx template: Copy/rename xxx-R6-3, update prefixes and build references, and tailor st.cmd and substitutions for your hardware.

Quick Start

Tell me: deploy synApps for my EPICS base at /opt/epics/base, use the default module set, and generate a new IOC from the xxx template named myioc.

Frequently Asked Questions about synapps-deploy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I assemble a consistent synApps support tree for EPICS?

To assemble a synApps support tree, use assemble_synApps to clone modules at tested tags and generate a unified buildable support layout, ensuring consistent module versions and reducing environment configuration errors.

What is the process to create and configure a new EPICS IOC from the xxx template?

Creating a new IOC from the xxx template involves copying and renaming the template directory, updating build references and prefixes with changePrefix, and tailoring st.cmd and substitutions files for your specific hardware configuration.

Can I override specific module versions or exclude modules when building synApps?

Yes, you can customize module selection in synApps by overriding specific module versions, excluding modules, or extending areaDetector submodules using command-line options like --set or a configuration file during the assemble_synApps process.

Does deploying synApps IOCs require manual edits to st.cmd and substitutions files?

Yes, deploying synApps IOCs requires manual edits to st.cmd and substitutions files after bootstrapping from the xxx template, ensuring hardware-specific configuration and prefix-renaming are correctly applied via changePrefix workflows.

What's the best way to automate EPICS IOC deployment and reduce build errors?

The best way to automate EPICS IOC deployment is using assemble_synApps to standardize module version selection and generate a unified buildable support tree, eliminating manual version tracking and reducing build configuration errors.