Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse

OpenLegacy Community

Global Moderators

Forum wide moderators

Private

Posts


  • Modernizing Legacy Development at Scale – Introducing OL Code
    roi.mR roi.m

    For decades, development on mainframe and IBM i systems required specialized terminals, manual build scripts, cryptic debugging methods, and limited collaboration. As enterprises modernize systems, migrate workloads, and expose legacy business logic to new platforms, the need for a modern development experience around COBOL and RPG has never been greater.

    OL Code was built precisely for this reality.

    It is not “just another editor” for COBOL or RPG.
    It is a developer workspace, migration accelerator, and visibility tool—engineered for integrators, migration teams, modernization architects, and IT departments.

    Why OL Code?

    As organizations reimagine their core applications, three needs repeatedly surface:

    Full visibility into the legacy estate
    Programs, copybooks, models, DB references, screen flows

    Structured development capabilities without depending on the terminal
    Editing, compiling, testing, running transactions

    A migration-aware, integration-friendly approach
    Generating APIs, refactoring screen programs, shifting logic into modern workflows

    OL Code was designed as the workbench where these needs converge.

    From Legacy Code to Modern Workflows—Professionally

    Full Mainframe/AS400 Workspace View

    OL Code provides structured navigation of:

    – Programs
    – Copybooks
    – Includes and dependencies
    – Variables and declarations
    – Linkage sections
    – Screen maps
    – DB2 files, tables, and SQL usage

    All visualized in a modern tree view, eliminating guesswork typically involved when tracing cross-file references.

    Dataset Browser & Real-Time Search

    Through seamless connectivity, teams can browse remote datasets:

    – PDS / PDSE libraries and members (z/OS)
    – Source libraries / file systems (IBM i)
    – Historical versions (where supported)

    Powerful search capabilities allow locating:

    – Variables
    – SQL queries
    – Called programs
    – Global fields
    – Copybook usage patterns

    This enables real dependency understanding within seconds—not days.

    Deep Analysis Layer, Powered by Hub Planner

    OL Code integrates with OpenLegacy Hub Planner to reveal insights such as:

    – Which program calls which program
    – What domains specific modules belong to
    – SQL access patterns
    – Variable usage and structure inheritance
    – Resource relationships (files, tables, screens, APIs)

    For integrators and migration teams, this means:

    – Impact analysis before modification
    – Controlled domain isolation
    – Clear modernization segmentation

    A True Modern IDE for COBOL & RPG

    Smart syntax view
    Coloring, folding, auto-alignment

    Code walkthrough
    Hover over fields to reveal type, origin, dependency relationships

    Variable and structure tracing
    Jump to definitions across project boundaries.

    Inline hints and recommendations

    Compiling at the Click of a Button

    OL Code enables:

    Compile COBOL program with one click

    Automatically sends:
    – Generation JCL (z/OS)
    – CRTBNDRPG / CRTSQLRPG / CRTPGM command (IBM i)
    – Bind/link steps

    Prebuilt templates for:
    – COBOL batch
    – CICS program
    – RPG service programs

    Compile Log Viewer
    Errors highlighted, missing references, bind failures

    AI-Assisted Compilation & Troubleshooting

    AI can:
    – Analyze compile errors
    – Suggest corrections
    – Apply fixes

    One-Click Testing — via OL Hub

    Execute programs remotely, validate response, replay test cases.

    Create APIs Directly from COBOL & RPG Code

    Outputs:
    – REST API structure
    – Mapping to fields
    – Code stubs
    – Reverse API bridge

    Screen Programs → RPC Programs

    AI-driven transformation using:
    – Structure inference
    – Screen state flattening
    – Request/response model creation

    Who Benefits Most?

    – Integration partners implementing cloud migration
    – Enterprises migrating gradually
    – Developers modernizing codebases
    – Migration factories

    Where OL Code Fits

    Assessment
    → browsing, impact analysis
    Segmentation
    → dependency understanding
    Refactoring
    → AI assisted code cleanup
    API enablement
    → generation & testing
    Migration
    → reverse API and coexistence
    Centralized Web Application Benefits
    OL Code runs as a modern web application, eliminating dependency on local machine installations.
    It can be installed centrally and accessed through standard browsers, giving users consistent access from anywhere.
    Typical deployment options include container‑based environments, standard enterprise runtime servers, and distributed runtime nodes close to mainframe and IBM i systems.
    This approach greatly simplifies IT operations and accelerates onboarding efforts.
    Teams can maintain a single system upgrade path, eliminating mismatched versions and reducing conflict resolution overhead.
    Security, access control and workspace configuration are managed centrally, ensuring governance and operational traceability.
    Centralized Web Application Benefits
    OL Code runs as a modern web application, eliminating dependency on local machine installations.
    It can be installed centrally and accessed through standard browsers, giving users consistent access from anywhere.
    Typical deployment options include container‑based environments, standard enterprise runtime servers, and distributed runtime nodes close to mainframe and IBM i systems.
    This approach greatly simplifies IT operations and accelerates onboarding efforts.
    Teams can maintain a single system upgrade path, eliminating mismatched versions and reducing conflict resolution overhead.
    Security, access control and workspace configuration are managed centrally, ensuring governance and operational traceability.
    Bottom Line

    OL Code delivers
    – Modern editing
    – Compile automation
    – Integrated testing
    – Migration workflows

    It is the modernization cockpit for mainframe and IBM i.

    Blogs

  • New version 1.6.6 is available!
    ohad.mO ohad.m

    🚀 New Features

    • Multiple Connections Configuration
      Administrators can now configure multiple connections for users to choose from, making it easy to switch between environments such as Test and Production.

    • Per-Connection Printer Queue
      The printer queue is now part of the connection properties, allowing each connection to define its own printer queue.

    • Favorite Connection Selection
      Users can mark a connection as their favorite. The emulator will automatically connect to it unless another connection is explicitly selected.

    • New Emulator Client Actions
      Added new client actions including Field Plus, Field Minus, New Line, Clear All Input Fields, and more.
      Refer to the keyboard mappings for available shortcuts.

    • AS400 Printer Panel Improvements

      • Printer spools can be filtered by time period
      • Multiple filters can be applied simultaneously (e.g., User and Queue)
    • AS400 SYSREQ Support
      Added AS400 System Request (SYSREQ) functionality
      (Default key binding: Shift + Esc)


    ✨ Enhancements

    • Improved Numeric Field Validation
      Alphabetic characters are no longer allowed in numeric fields. Users will be notified when invalid input is entered.

    • Persistent Zoom Level
      The zoom level is now saved between sessions—no need to readjust it every time.

    • Copy Entire Screen
      The full screen can be copied without selecting text by invoking the Copy Screen action (Ctrl + C) with no active selection.

    • Improved Handling of Multi-line Fields

    OL Terminal

  • Release note v1.5.2
    roi.mR roi.m

    Release Notes

    Version 1.5.2 (Latest)

    Release Date: January 20, 2026
    Commit Range: ecc9efd → e4c72d2


    🎯 Overview

    This release includes significant feature enhancements, security improvements, and infrastructure updates. The version has progressed from 1.4.3 to 1.5.2, introducing major new capabilities in query management, schema visualization, and version management.


    ✨ Major Features

    Query Console Enhancements

    • Saved Queries Functionality: New ability to save, manage, and reuse SQL queries
      • Save queries with custom names and descriptions
      • Browse and load saved queries from a dedicated dialog
      • Enhanced query persistence and retrieval
    • Row Modification Handling: Dynamic UPDATE statement generation for query results
      • Improved CRUD operations in Query Console
      • Enhanced SQL query handling and logging

    Schema Management

    • Schema Creation Prompt: New prompt in connection dialog to create schemas when needed
    • Foreign Key Enrichment: Enhanced schema graph visualization with JDBC foreign key relationships
      • Improved schema graph retrieval with better error handling
      • Enhanced metadata service capabilities

    Hub Integration Improvements

    • Enhanced SQL Query Handling: Improved integration with Hub for asset creation
      • Stored Procedure Support: Added support for CALL statements in SQL queries
      • Procedure Name Extraction: Enhanced table/procedure name extraction from CALL statements with proper normalization
      • Kebab-case Naming: Automatic kebab-case conversion for stored procedures with '-sp' suffix
      • Schema Qualification: Updated query generation prompts to require schema qualification for table names
      • CRUD Dialog Enhancements: Improved user experience with clearer labels (Operation name → Model name)
    • Enhanced Logging & Debugging: Comprehensive logging improvements in HubService
      • Detailed logging for asset creation operations including input parameters and payload structure
      • Enhanced error messages with full request/response context
      • Better debugging information for Hub API interactions
    • Query Console Integration: Improved Query Console integration with Hub
      • Enhanced WHERE clause condition management (AND to OR logic improvements)
      • New methods for better condition management and grouping
      • Added schemaName field to chat for improved context in query generation
      • Better integration between Query Console and Hub asset creation workflows

    Version Management

    • Version Display & Management: Complete version management system implementation
      • Version displayed in application UI (title bar badge)
      • Version API endpoint (/api/v1/version) for runtime version access
      • Version information in startup logs and JAR manifest
      • Automatic version reload on authentication state changes

    🔒 Security Improvements

    Dockerfile Enhancements

    • Removed Python packages to fix multiple CVEs:
      • CVE-2018-20225, CVE-2025-8869, CVE-2023-5752 (pip)
      • CVE-2025-47273, CVE-2024-6345, CVE-2022-40897 (setuptools)
    • Enhanced security configuration for production deployments

    Dependency Updates & CVE Fixes

    • Netty: Updated to 4.1.129.Final (fixes CVE-2025-67735)
    • Protobuf: Updated to 3.25.5 (fixes CVE-2024-7254)
    • Dependency version management improvements in build.gradle.kts
    • Vert.x and Logback version adjustments for compatibility

    🛠️ Infrastructure & Developer Experience

    Version Management Automation

    • Unified Version Bump Scripts: New tag-and-bump.sh script for streamlined version management
      • Single script for version bumping and tagging
      • Support for patch, minor, and major version increments
      • Automatic synchronization between gradle.properties and frontend/package.json
    • Release Workflow Documentation: Comprehensive guides added
      • RELEASE_WORKFLOW.md: CI/CD integration guide
      • VERSIONING.md: Complete version management documentation

    📊 Statistics

    • Total Commits: 28 commits
    • Files Changed: 44 files
    • Lines Added: ~3,406 insertions
    • Lines Removed: ~246 deletions
    • Net Change: +3,160 lines

    Key File Changes

    • Frontend: Query Console, Saved Queries components, Connection Dialog enhancements
    • Backend: Hub Service, Metadata Service, Query Service improvements
    • Infrastructure: Dockerfile, build configuration, version management scripts
    • Documentation: Release workflow, versioning guides

    🔄 Version Progression

    • 1.4.3 → 1.4.4: Version management infrastructure
    • 1.4.4 → 1.4.6: Version bump script improvements
    • 1.4.6 → 1.4.7: Foreign key enrichment
    • 1.4.7 → 1.4.8: Schema creation prompt, version display enhancements
    • 1.4.8 → 1.4.9: JSON parsing improvements
    • 1.4.9 → 1.5.0: Saved queries functionality, Dockerfile security
    • 1.5.0 → 1.5.1: Dependency compatibility adjustments
    • 1.5.1 → 1.5.2: CVE fixes, final dependency updates

    📝 Notable Changes by Component

    Frontend (frontend/)

    • New saved queries dialog components
    • Enhanced query console with save/load functionality
    • Improved connection dialog with schema creation prompt
    • Version badge in application header
    • Enhanced CRUD dialog components

    Infrastructure

    • Dockerfile security hardening
    • Build configuration updates for CVE fixes
    • Version management scripts and documentation
    • Enhanced logging configuration

    🚀 Migration Notes

    • Version Display: Version is now automatically displayed in the UI. No action required.
    • Saved Queries: New feature available immediately. Existing queries are not migrated automatically.
    • Dependencies: Ensure Docker images are rebuilt with the updated Dockerfile for security fixes.
    • Version Management: Teams can now use the new tag-and-bump.sh script for version management.

    🔗 Related Pull Requests

    • PR #16: Schema graph foreign key enrichment

    Note: This release represents a significant milestone with major feature additions, security improvements, and enhanced developer tooling. All users are encouraged to upgrade to benefit from the new features and security fixes.

    SQOL

  • Release Notes v1.4.0
    roi.mR roi.m

    Release Notes

    Release Date: January 4, 2026
    Commit Range: 1fb65668be92f706fb3347e0b9aa78c24d4603dc to c0adef4


    🎯 High-Level Summary

    Query Console Enhancements

    Interactive Data Editing & Management

    • Direct cell editing in query results with inline editing for short values and dialog-based editing for long values
    • Visual tracking of modified rows with protected primary key columns
    • One-click UPDATE/DELETE statement generation with automatic WHERE clause creation using primary keys
    • Column sorting with type-aware ordering and automatic ORDER BY clause generation

    Database Schema Management

    Comprehensive Schema Tools

    • Stored procedures browser with metadata viewing and automatic CALL statement generation
    • Visual table designer for CREATE TABLE and ALTER TABLE operations with database-specific DDL generation
    • Interactive schema graph visualization showing tables, relationships, and foreign keys with pan/zoom capabilities

    Hub Integration & Settings

    Enhanced Hub Workflow

    • Personal Hub settings configuration with local storage and admin-controlled visibility
    • Collapsible SQL query editing panel with JDBC style conversion
    • Enhanced asset name suggestions based on SQL operations
    • Success dialogs with OL Hub URL display for created assets

    Query Chat & AI Features

    Intelligent Query Assistance

    • Prompt suggestions for data analysis and schema improvements
    • SQL query extraction from chat messages with direct execution capability
    • Schema optimization recommendations (normalization, indexing, partitioning)
    • Foreign key relationship analysis and referential integrity suggestions

    Connection & Admin Management

    Improved Configuration

    • Schema autocomplete in connection dialog with refresh functionality
    • Admin settings for Hub UI URL configuration
    • Enhanced tooltips and user guidance throughout the application
    • Tab management and conditional log visibility in admin panel

    Editor & UI Improvements

    Modern Development Experience

    • Monaco Editor integration for enhanced SQL editing with syntax highlighting
    • Improved visual styling and user feedback across components
    • Signal-based state management for better reactivity and synchronization

    SQOL

  • # Release Notes for v1.3.5
    roi.mR roi.m

    Query Console Enhancements

    • Nested Table Tree Structure (7186692)
      • Replaced table selection list with a nested tree structure for better organization
      • Implemented context menus for table actions (create, alter, drop)
      • Added table selection toggle and improved table details management
      • New dialog for creating and altering tables
      • Enhanced layout and responsiveness
    • Full Schema Loading & Inline Editing (5ffb78e)
      • Background loading of full schema data for improved metadata management
      • Inline editing for table cells with direct value modification
      • Temporary and modified row tracking for unsaved changes
      • Confirmation dialogs for unapplied modifications
      • Enhanced error handling and user feedback
    • Query History (50cd30a)
      • New history dialog for previously executed queries
      • QueryHistoryService for managing query history per connection
      • Ability to select and reuse past queries
      • Improved data organization and user experience
    • Table Details Toggle (c1c8285)
      • Button to toggle visibility of table details
      • Improved layout handling for overflow
      • Better responsiveness across different screen sizes

    Data Export & Import

    • CSV Export (458125d)
      • Export query results to CSV format
      • Copy results to clipboard functionality
      • User feedback via snack bars for operations
    • JSON Schema Export (e3eb18a)
      • Export selected table schemas to JSON files
      • Backend POST /export-json endpoint
      • Export mode selection via radio buttons
    • JSON Schema Import (1020be2)
      • Import table schemas from JSON files
      • Option to override existing tables with drop option
      • Backend POST /import-json endpoint
      • File upload dialog with connection selection

    Connection Management

    • Clone Connection (c0755b9)
      • Clone existing database connections
      • Automatic unique name generation
      • Clears sensitive information (IDs, passwords) for cloned connections
      • Updated UI layout for clone action button

    Query Chat Enhancements

    • Sample Query Generation (4457b2b)
      • Display sample queries for selected tables
      • Generate sample INSERT statements for up to five tables
      • Improved UI/UX for sample links and buttons

    Utilities

    • Copy Table Details (bf53827)
      • Copy table name and column details to clipboard
      • Error handling and user feedback via snack bars

    Bug Fixes

    • Token Fix (cdf496a)
      • Fixed token-related issue

    Other Changes

    • Merge Updates (e0c1083)
      • Merged latest changes from main branch

    Summary

    This release includes significant enhancements to the Query Console, including a complete revamp with nested table tree structure, inline editing capabilities, query history, and comprehensive export/import functionality. The connection management has been improved with clone functionality, and the Query Chat component now supports sample query generation.
    Total Commits: 12 (excluding merge commits)
    Contributors: roi0507, Eddie

    SQOL

  • SQOL Updates Dec 09 25
    roi.mR roi.m
    • Added Chat support (with full schema in context)
    • Solved navigation issues
    • Added ability to click on table details columns or result columns to add WHERE automatically

    185991a8-5b01-4c18-8006-95b856190761-image.png

    SQOL

  • Modernizing Green-Screen Access: Introducing OL Terminal for TN3270 & TN5250
    roi.mR roi.m

    Modernizing Green-Screen Access: Introducing OL Terminal for TN3270 & TN5250

    For decades, TN3270 and TN5250 terminals have been the gateway to mission-critical systems on IBM mainframe and IBM i. These systems still run the heart of many enterprises, but the access method has barely changed. Traditional desktop terminal clients introduce cost, maintenance, and security risks.

    OL Terminal changes that completely.

    OL Terminal provides a modern, browser-based experience that mirrors traditional green-screen environments, but with centralized management, secure access, and zero desktop dependencies.


    A Terminal Experience with No Installation

    Users simply open a browser and start working. There is nothing to install, update, or distribute. This eliminates:

    • MSI rollouts
    • Admin permissions
    • Manual configuration
    • Version inconsistencies across locations

    Any authorized user with a browser can access the host immediately.


    Secure Access Over HTTPS

    Traditional terminal connections often rely on unsecured TN streams. OL Terminal runs natively over HTTPS, introducing enterprise-grade security:

    • Central authentication
    • Encrypted sessions
    • SSO compatibility
    • Access control and auditing

    Remote workers operate with secure connectivity without requiring desktop VPN-installed emulators.


    Real-Time Terminal Interaction with WebSockets

    OL Terminal communicates using WebSockets, providing responsive user interaction:

    • Instant screen refreshes
    • Synchronized cursor position
    • Reliable keystroke delivery
    • Low latency even across distance

    The result is a true 1:1 experience comparable to classic installed emulators.


    Productivity Enhancements

    OL Terminal preserves a familiar terminal interface while introducing enhanced usability:

    Macros

    Automate multi-step sequences up to full process flows.

    Type-Ahead Support

    Users can continue entering commands even during screen transitions.

    Keyboard Mapping

    Define key layouts suitable for modern devices and user preferences.

    Print-to-PDF

    Export screens and workflows directly to PDF, without hardware printers.


    Centralized IT Control and Visibility

    Traditionally, green-screen usage is invisible once installed on desktops. OL Terminal changes this.

    Admin Session Viewer

    Support teams can observe session interaction live for:

    • Issue diagnosis
    • Training
    • Operational support

    Policy Enforcement

    Connection entry points, timeout values, routing paths, and identity rules can be defined centrally.

    Session Inventory

    Gain visibility into who is connected, where, and to which system.

    This simplifies support, audit readiness, and usage monitoring.


    OL Hub Integration – From Screens to APIs

    Combined with OpenLegacy Hub, OL Terminal helps organizations modernize screen-based transactions.

    Real session usage can be translated into:

    • Logical screen structures
    • Input/output data definitions
    • Sequence flows
    • Dynamic field relationships

    These are surfaced as screen-based APIs without modifying COBOL, RPG, or existing transactions.

    For example, customer lookup screens can become REST APIs using real navigation patterns observed through OL Terminal sessions.

    This lets organizations gradually migrate business workflows into digital channels.


    OpenLegacy TermIQ – Analytics, Insights & Auditing

    TermIQ extends OL Terminal with usage intelligence:

    • Identify frequently used screens
    • Measure operational efficiency
    • Detect repeated errors
    • Audit user navigation
    • Track processing time

    Examples of insights:

    • Why processing time differs across teams
    • Which flows frequently reach exception screens
    • Where user training gaps appear

    This visibility was previously unavailable in traditional emulation models.


    When OL Terminal Provides Maximum Value

    OL Terminal is ideal for:

    • Customer support centers
    • Back-office and processing teams
    • Distributed branches
    • Remote and offshore workers
    • Testing environments
    • Training environments

    All gain modern browser access without rollout effort.


    Why OL Terminal Matters

    OL Terminal uniquely combines:

    1. User familiarity — same screens, same workflow
    2. Centralized IT ownership — controlled access, observable sessions
    3. Modernization readiness — terminal flows become APIs and analytics inputs

    And the solution is free to use, lowering barriers for IT teams.


    Summary

    Area Value
    Access Web-based, no installation
    Security HTTPS encrypted access
    Operations Session visibility and control
    Productivity Macros, type-ahead, PDF export
    Modernization Screen-to-API creation with OL Hub
    Analytics TermIQ tracking, behavior insight

    OL Terminal modernizes access to mainframe and IBM i systems while preserving operational familiarity and offering IT new layers of visibility, control, and modernization opportunity.

    Simple to deploy. Secure by design. Free to use.

    This is the new standard for terminal access.

    Blogs

  • Launch all apps from docker compose
    roi.mR roi.m

    Streamline Your OpenLegacy Development with Docker Compose

    Introduction

    If you're working with OpenLegacy tools, you know the pain of managing multiple services, configuring ports, and keeping track of different Docker commands. Today, I'm sharing a simple Docker Compose setup that brings all your OpenLegacy development tools together in one place, with a beautiful homepage to boot!

    The Problem

    Running OpenLegacy tools typically involves:

    • Memorizing (or constantly looking up) long docker run commands
    • Managing multiple container instances manually
    • Tracking which port runs which service
    • Dealing with volume permissions and data persistence
    • Remembering to set environment variables correctly

    It's tedious, error-prone, and takes you away from what matters: building great applications.

    The Solution

    I've created a streamlined Docker Compose configuration that launches all your OpenLegacy tools with a single command. The setup includes:

    • 🏠 A Beautiful Homepage (localhost:8080) - No more bookmarking multiple ports! A clean, modern landing page shows all your tools at a glance
    • 💻 OL Terminal (localhost:8081) - Your terminal-based development environment
    • ⚡ OL Code (localhost:8082) - Full-featured code editor
    • 🗄️ SQOL (localhost:8083) - SQL and data management interface

    Key Features

    One Command to Rule Them All

    Gone are the days of copy-pasting Docker commands. Just run:

    ./apps.sh start
    

    That's it. All services spin up, properly configured, with persistent data volumes.

    Centralized Configuration

    All credentials and licenses are managed in a single config.env file. Update once, apply everywhere. No more hunting through Docker commands to change a password or license key.

    Smart Data Persistence

    Your work is automatically saved in named Docker volumes that survive restarts, updates, and even system reboots. Data only disappears if you explicitly delete it—no more "where did my data go?" moments.

    Permission Issues? Solved.

    The setup runs containers with proper permissions out of the box. No more FileNotFoundException or permission denied errors when tools try to write configuration files.

    Professional Homepage

    The included landing page isn't just functional—it's genuinely nice to look at. With a modern gradient design, hover animations, and responsive layout, it makes accessing your tools a pleasure rather than a chore.

    Getting Started is Easy

    1. Clone the repository
    2. Copy your OpenLegacy license from your Community profile
    3. Paste it into config.env
    4. Run ./apps.sh start
    5. Visit http://localhost:8080

    That's the entire setup. No complex configuration, no troubleshooting, no headaches.

    Perfect for Teams

    The beauty of this setup really shines in team environments:

    • Consistent environments - Everyone runs the same configuration
    • Easy onboarding - New team members are productive in minutes
    • Version controlled - Check the compose file into Git (excluding the sensitive config.env)
    • Documentation included - Comprehensive README covers all common scenarios

    Beyond the Basics

    The helper script (apps.sh) provides convenient commands for common tasks:

    ./apps.sh logs     # View real-time logs
    ./apps.sh status   # Check service health
    ./apps.sh restart  # Quick restart
    ./apps.sh pull     # Update to latest versions
    

    It also automatically loads environment variables from config.env, ensuring your configuration is always in sync.

    Technical Highlights

    For those interested in the implementation details:

    • Uses official OpenLegacy ECR images
    • Lightweight nginx:alpine for the homepage (just 40MB!)
    • Named volumes for data persistence
    • Root user execution to avoid permission issues on Windows/Mac
    • Environment variable interpolation for flexible configuration
    • Restart policies for automatic recovery

    Conclusion

    This Docker Compose setup transforms OpenLegacy development from a juggling act into a smooth, professional workflow. Whether you're a solo developer or part of a larger team, having all your tools accessible from a single, beautiful interface makes a real difference in daily productivity.

    The entire setup is open and ready to use. Fork it, customize it, make it your own. Happy coding!


    Repository: https://github.com/openlegacy/apps-manager
    License: OpenLegacy
    Contributions: Welcome!

    Have questions or suggestions? Drop them in the issues section or reach out through the OpenLegacy Community.

    Announcements

  • New version 1.5.1 is available!
    roi.mR roi.m
    • Ability to use mock session with trail file. Demo trails are available out of the box for mainframe and AS/400 cards demo
    • Zip package (JAR deployment) now contains mainframe.sh and as400.sh scripts for deploy/start/stop JAR on a remote host via SCP & SSH
    OL Terminal

  • Any plans to support TN3270E?
    roi.mR roi.m

    Hi @JZZSMB_gme , new version is available with JAR deployment on z/OS is available:
    https://forum.community.openlegacy.com/topic/23/new-version-1.4.8-is-available

    OL Terminal

Member List

O openlegacy
roi.mR roi.m
ol-prodO ol-prod
ohad.mO ohad.m
ruslan.aR ruslan.a
  • Login

  • Login or register to search.
Powered by NodeBB Contributors
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups