OpenLegacy Community

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 Clone the repository Copy your OpenLegacy license from your Community profile Paste it into config.env Run ./apps.sh start 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.

As CTO of OpenLegacy, I’m excited to welcome you to our OpenLegacy Community site. When we launched this space, we had a clear vision: make legacy modernization approachable, practical, and accessible to everyone. That’s why we decided to provide three of our core tools—OL Terminal, OL Code, and SQOL—completely free. This isn’t just about handing out free software. It’s about lowering the barriers to modernization, empowering developers, and creating a shared place where enterprises and individual technologists alike can experiment, learn, and build. Why Free? Modernization projects are complex. They involve risk, multiple moving parts, and a steep learning curve. We know this from years of experience with enterprises worldwide. By offering these tools for free, we’re: Democratizing access: Anyone can explore mainframe, IBM i, or database modernization without worrying about licenses. Encouraging experimentation: Developers can try ideas quickly—whether that’s connecting to a mainframe, exploring SQL on a legacy DB, or analyzing COBOL code—without budget approvals slowing them down. Building community trust: Free tools open the door for collaboration, feedback, and improvement that benefit everyone. Why Browser-Based? We’re living in a world of SaaS, collaboration, and remote work. Installing heavy clients is the old way. With browser-based apps, you get: Zero install, instant access: Just open a link and start working. Cross-platform consistency: Whether you’re on Windows, Mac, Linux, or even a Chromebook—your experience is the same. Enterprise readiness: Browser-first means easier deployment, controlled access, and future integration with cloud and DevOps pipelines. For us, insisting on browser-based wasn’t optional—it was the only way to align with where enterprises are headed. The Three Free Apps ️ OL Terminal A modern web-based 3270/5250 terminal client. Connect to mainframes and IBM i systems directly from your browser. Full support for terminal models, colors, and session management. Perfect for training, testing, or even production access when paired with enterprise security. OL Code A lightweight legacy code IDE, built for COBOL, RPG, and more. Syntax highlighting, structure navigation, and copybook handling—all in the browser. Designed to help developers understand and modify legacy codebases without heavy desktop tools. A stepping stone to deeper analysis and modernization workflows. ️ SQOL A browser-based database console, tuned for legacy and modern databases. Run queries, browse tables, and explore data instantly. Works with DB2, Oracle, MySQL, and more. Ideal for quick checks, learning SQL, or setting up modernization test cases. What’s In It for Us? We believe in mutual value. By giving these tools for free, we: Invite you into the OpenLegacy ecosystem. As you use the free tools, you’ll see how they connect naturally with our enterprise OpenLegacy Hub, which adds advanced capabilities like API generation, testing, governance, and integration. Enable real modernization journeys. Start free with OL Terminal, OL Code, or SQOL. When your needs grow—building APIs, managing modernization patterns, ensuring enterprise-grade coexistence—you’re already aligned with OpenLegacy’s platform. Build a stronger community. Every developer who tries these tools, shares feedback, or contributes ideas helps us make modernization better for all. Collaboration With the Community We don’t just want people to use these tools—we want to learn from you. Share your use cases: How are you using OL Terminal, OL Code, or SQOL in your environment? Suggest improvements: Tell us what works, what’s missing, and what would make these tools even more valuable. Co-create modernization practices: Together, we can define best practices for legacy systems that reflect real-world experience, not just theory. Your input helps shape the roadmap, improves the tools for everyone, and makes modernization less of a challenge and more of a community-driven journey. The Next Step Explore the free tools today: OL Terminal OL Code SQOL And when you’re ready, see how they scale into enterprise modernization with the OpenLegacy Hub. Together, we can simplify modernization, reduce risk, and unlock the future of your core systems. I personally invite you to join the community forum, share your experiences, and collaborate with us. The more we learn from each other, the stronger our community—and our modernization journey—becomes. — Roi Mor, CTO, OpenLegacy

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

This forum is the dedicated space for everything related to OL-Code — our modern, web-based IDE for COBOL, RPG, JCL, and other legacy languages. Whether you’re here to explore features, troubleshoot issues, or share insights, this is the place to connect with the community and the OpenLegacy team. What You Can Do Here Ask questions about OL-Code functionality and usage Share tips, workflows, and best practices for legacy code development Report issues or unexpected behavior Learn from others and help fellow developers Stay updated with new features and improvements Reporting Issues If you come across a problem: Search the forum first to see if it’s already been reported or solved. If not, create a new topic with clear details (language, steps to reproduce, error messages, screenshots if possible). Use descriptive titles and tags so others can find your post easily. Forum Guidelines To keep this forum helpful and collaborative, please follow these rules: Be respectful and professional — no harassment or personal attacks. Stay focused — discussions should be about OL-Code. Avoid duplicates — check before posting a new topic. Share knowledge — if you’ve solved a problem, please post the solution. Be constructive — when reporting issues, provide details and suggestions when possible. A Community for Legacy Innovators OL-Code brings a modern developer experience to legacy systems — and this forum is here to help you get the most out of it. The OpenLegacy team will engage here, but your contributions and peer-to-peer support are what make this space truly valuable. Welcome to the OL-Code community, and happy coding!

This forum is the dedicated space for everything related to SQOL — our Universal SQL Console. Whether you’re here to explore features, troubleshoot issues, or share insights, this is the place to connect with the community and the OpenLegacy team. What You Can Do Here Ask questions about SQOL functionality and usage Share tips, workflows, and best practices for legacy code development Report issues or unexpected behavior Learn from others and help fellow developers Stay updated with new features and improvements Reporting Issues If you come across a problem: Search the forum first to see if it’s already been reported or solved. If not, create a new topic with clear details (language, steps to reproduce, error messages, screenshots if possible). Use descriptive titles and tags so others can find your post easily. Forum Guidelines To keep this forum helpful and collaborative, please follow these rules: Be respectful and professional — no harassment or personal attacks. Stay focused — discussions should be about SQOL. Avoid duplicates — check before posting a new topic. Share knowledge — if you’ve solved a problem, please post the solution. Be constructive — when reporting issues, provide details and suggestions when possible. A Community for Legacy Innovators SQOL brings a modern developer experience to legacy systems — and this forum is here to help you get the most out of it. The OpenLegacy team will engage here, but your contributions and peer-to-peer support are what make this space truly valuable. Welcome to the SQOL community, and happy coding!