Split embedded eic-shell heredocs into template files, assembled via Jinja2

[Copilot]

install.sh embedded two large heredocs (~180 lines total) for generating the Singularity and Docker eic-shell launchers inline, making the script bloated and the templates hard to maintain independently.

Changes

Template files

• eic-shell.singularity — Singularity launcher extracted from install_singularity()
• eic-shell.docker — Docker launcher extracted from install_docker(), including the macOS X11 block as natural shell code gated by a runtime $(uname -s) check

Both files are proper standalone shell scripts using ${VAR:=default} bash defaults for all install-time variables, so they can be run or linted directly (set the relevant env vars to override the defaults for testing). There are no ${EICS_*} pseudo-variables.

Launcher generation in install.sh

Install-time values are baked into the generated eic-shell script in two steps:

# 1. Write a preamble with actual install-time values (bash variable expansion)
cat > eic-shell <<PREAMBLE#!/bin/bashORGANIZATION="$ORGANIZATION"CONTAINER="$CONTAINER"INSTALLED_SINGULARITY="$SINGULARITY"...PREAMBLE# 2. Append the template body (skip its own shebang)
tail -n +2 "$SCRIPT_DIR/eic-shell.singularity">> eic-shell

Assembly for distribution

• assemble.py — Uses jinja2.Environment(loader=FileSystemLoader(...)) to load each template file cleanly, then replaces the tail -n +2 "$SCRIPT_DIR/TEMPLATE" >> OUTPUT calls with equivalent inline heredocs, producing a self-contained install.sh suitable for curl … | bash distribution. A post-assembly validation raises an error if any $SCRIPT_DIR/ reference survives.

CI deploy workflow

• .github/workflows/deploy.yml — Extended (from the existing workflow) to install jinja2 and run assemble.py before building the Jekyll site, so the assembled standalone install.sh is published to GitHub Pages on every push to main.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Reduce duplication in eic-shell script embedded install.sh</issue_title>
<issue_description>Is your feature request related to a problem? Please describe.
There is a significant amount of duplication here, but it is pre-existing.

Describe the solution you'd like
In order to not make duplication worse, we should split off the embedded eic-shell heredocs into separate files and read them in with envsubst. We should modify the CI workflow to publish a complete single install.sh at the current path.
</issue_description>

Comments on the Issue (you are @copilot in this section)

• FixesReduce duplication in eic-shell script embedded install.sh #26

---

💬 Send tasks to Copilot coding agent from Slack and Teams to turn conversations into code. Copilot posts an update in your thread when it's finished.

[Copilot]

Pull request overview

This PR refactors the install.sh launcher generation by moving the embedded Singularity/Docker eic-shell scripts into dedicated template files and using envsubst for substitution, with a CI workflow to publish a self-contained assembled installer for curl | bash usage.

Changes:

• Extract eic-shell launchers into eic-shell.singularity and eic-shell.docker templates, generated via envsubst from install.sh.
• Add assemble.py to inline templates back into a standalone install.sh for distribution.
• Add a GitHub Pages publish workflow that assembles and deploys install.sh on pushes to main.

Reviewed changes

Copilot reviewed 5 out of 6 changed files in this pull request and generated 10 comments.

Show a summary per file

File	Description
install.sh	Uses envsubst + $SCRIPT_DIR templates to generate the eic-shell launcher.
eic-shell.singularity	New Singularity launcher template to be substituted at install time.
eic-shell.docker	New Docker launcher template (including the macOS X11 logic) to be substituted at install time.
assemble.py	Generates a standalone install.sh by replacing template reads with inline heredocs.
.github/workflows/publish.yml	Builds and deploys the assembled install.sh to GitHub Pages.
.gitignore	Ignores Python __pycache__/.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review. Take the survey.

[netlify]

❌ Deploy Preview for kaleidoscopic-syrniki-0cfb8a failed.

Name	Link
🔨 Latest commit	c199be7
🔍 Latest deploy log	https://app.netlify.com/projects/kaleidoscopic-syrniki-0cfb8a/deploys/69b5c7a968cc810008032e7b

[wdconinc]

@copilot Target branch calls this file deploy.yml. Instead of creating a new file, integrate into the target branch's deploy.yml workflow.

[Copilot]

Done in 42c57e1 — integrated the "Assemble standalone install.sh" step into the existing deploy.yml and removed publish.yml.

[wdconinc]

@copilot I don't like the envsubst replacement in assembly.py; it's hacky. Consider if a templating engine like jinja2 would be better here. The target is two goals:

• a way to run the install.sh script locally for testing,
• a way to provide a combined install.sh script that does not depend on external files.

The goals would be best accomplished by allowing the embedded shell scripts to be treated as shell scripts in the repository, not as embedded heredocs (the main motivation for this change).

[Copilot]

@copilot I don't like the envsubst replacement in assembly.py; it's hacky. Consider if a templating engine like jinja2 would be better here. The target is two goals:

• a way to run the install.sh scri...

Done in c199be7. Here's what changed:

Template files are now proper shell scripts — ${EICS_*} pseudo-variables are gone. Both eic-shell.singularity and eic-shell.docker now use ${VAR:=default} bash defaults at the top, so they can be run or linted as standalone scripts (just set the relevant env vars for a real test). The #!/bin/bash shebang is preserved.

install.sh — no more envsubst — the export EICS_* … envsubst … < "$SCRIPT_DIR/template" blocks are replaced by:

1. An unquoted heredoc (cat > eic-shell << PREAMBLE) that writes the shebang and bakes in all install-time values via normal bash variable expansion.
2. tail -n +2 "$SCRIPT_DIR/template" >> eic-shell which appends the template body (skipping its own shebang since the preamble already provides one).

assemble.py — Jinja2 FileSystemLoader — template files are loaded via jinja2.Environment(loader=FileSystemLoader(...)). The regex is much simpler: it matches the unambiguous tail -n +2 "$SCRIPT_DIR/FILE" >> OUTPUT lines and replaces them with quoted heredocs. A post-assembly check raises an error if any $SCRIPT_DIR/ reference survives. deploy.yml gains a pip install jinja2 step.