Launch all apps from docker compose

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

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.