FASRC OnDemand Loop Deployment Builds

This repository contains the configuration and automation pipeline used to manage deployment builds for the OnDemand Loop application, tailored for the Cannon and FASSE clusters at FASRC.

The Harvard Dataverse landing page to inform users of the access requirements to use OnDemand Loop is managed in this repo.
Production landing page: https://hmdc.github.io/fasrc-ondemand-loop/dv_external_tools/landing.html
QA landing page: https://hmdc.github.io/fasrc-ondemand-loop/qa/dv_external_tools/landing.html

Overview

• 🚀 Deployment Build Management
  Orchestrates creation of QA and production builds via GitHub Actions, driven by issue comments and labels.

• ⚙️ FASRC-Specific Configuration
  Hosts and maintains the environment-specific configuration needed to deploy OnDemand Loop as a Passenger application within FASRC.

• 🧭 Dataverse External Tools Landing Page
  Improves UX for Dataverse users without an FASRC account by explaining access requirements to OnDemand Loop.

• 🧩 Separation of Concerns
  Application code lives in IQSS/ondemand-loop.
  This repository builds and deploys that code into FASRC environments.

Usage (Source of Truth)

To create QA or Production deployment builds, use the Deployment Build issue template and follow the instructions at the top of the template.
This keeps instructions centralized and avoids duplication or drift in the README.

• Open a new issue using the Deployment Build template (via New issue → Deployment Build).
• Follow the template’s embedded steps (slash commands, approvals, promotions, etc.).
• The workflows read the issue’s labels and hidden comments to coordinate builds and deployments.

➡️ Template: Deployment Build issue template

ℹ️ The issue template is the canonical reference for creating builds. If a process changes, update the template—no README edits required.

Local Testing

You can test the FASRC configuration locally before deploying to production environments:

make dev_up

This command will:

1. Create a build/ directory
2. Clone the OnDemand Loop repository
3. Build the application with make loop_build
4. Apply FASRC-specific configuration from config/fasrc/
5. Start the development environment

Access the Application

Once running, visit: https://localhost:33000/pun/sys/loop

Test credentials: ood / ood

Options

• Default: Uses OnDemand Loop main branch
• Release branch/tag: make dev_up TAG=loop-branch-name
• Update existing: make update (fetches latest changes)

⚠️ Self-Signed Certificate Warning
Your browser will show a security warning due to the self-signed SSL certificate. You can safely proceed by accepting the exception.

Environment

This repository:

• Runs GitHub Actions to coordinate builds and deploy GitHub Pages.
• Prepares the application with FASRC-specific configs.
• Publishes artifacts to the appropriate locations.
• Does not deploy servers directly—deployment to FASRC hosts is handled externally (e.g., via Puppet).

Project Structure

• .github/workflows/ — Build and deployment automation workflows
• .github/scripts/ — Shared utility scripts for workflow logic
• config/fasrc — FASRC-specific configuration
• docs/ — Troubleshooting guides and documentation
  • LOOP_TROUBLESHOOTING.md — OnDemand Loop troubleshooting guide
  • OOD_DASHBOARD_TROUBLESHOOTING.md — Open OnDemand troubleshooting guide
  • Additional OOD troubleshooting documentation (coming soon)
• dv_external_tools/ — Static HTML landing page integrated with Harvard Dataverse

Requirements

• Only authorized users may run deployment commands via issue comments.
• Production promotions require explicit approval, as described in the Deployment Build issue template.