Conversation
- Added `.devcontainer` configuration for setting up a fully functional dotCMS development environment in GitHub Codespaces. - Included setup for Docker, PostgreSQL, OpenSearch, and required dependencies. - Integrated VS Code extensions, port forwarding, and developer tooling. - Added scripts (`setup.sh` and `post-start.sh`) to initialize and provide status updates for development services.
- Simplified setup instructions in `.devcontainer/README.md` by removing redundant options. - Unified build command structure for easier usage. - Increased `post-start.sh` readiness timeout to improve container stability. - Fixed `dockerComposeVersion` typo in `devcontainer.json`. - Removed unused Java configurations and environment variables.
…cker-in-docker` feature - Added a wait loop in `setup.sh` to ensure Docker daemon is ready before proceeding. - Replaced `docker-outside-of-docker` with `docker-in-docker` in `devcontainer.json` for better compatibility.
- Improved Docker readiness logic in `setup.sh`, including workspace detection and Docker Compose command resolution. - Enhanced feedback for missing or misconfigured dependencies. - Adjusted `docker-in-docker` feature version in `devcontainer.json` for compatibility.
…ve unused mounts
…tion and Docker management - Simplified workspace root resolution using Git. - Improved Docker readiness wait loop and extended timeout. - Updated Docker Compose configuration to use subfolder structure. - Enhanced error handling and messaging for missing dependencies.
… workspace initialization - Improved workspace root detection using Git and added error handling for non-Git environments. - Updated Docker Compose command resolution to prioritize v2. - Enhanced readiness checks for Docker daemon and dotCMS service with detailed feedback. - Simplified and clarified quick command outputs for Docker management.
…ions and updating debug setups for dotCMS
…etailed development workflows and redundant sections
❌ Issue Linking RequiredThis PR could not be linked to an issue. All PRs must be linked to an issue for tracking purposes. How to fix this:Option 1: Add keyword to PR body (Recommended - auto-removes this comment)
Why is this required?Issue linking ensures proper tracking, documentation, and helps maintain project history. It connects your code changes to the problem they solve.--- This comment was automatically generated by the issue linking workflow |
1 participant
Claude finished @erickgonzalez's task —— View job
PR Description: GitHub Codespaces Development Environment
This PR introduces a complete GitHub Codespaces configuration for dotCMS, enabling developers to spin up a fully functional development environment in the cloud within minutes.
Tasks:
🎯 What This PR Adds
New Files Added:
.devcontainer/devcontainer.json(144 lines) - Main Codespaces configuration.devcontainer/setup.sh(93 lines) - Environment setup and service initialization script.devcontainer/post-start.sh(115 lines) - Status monitoring and user guidance script.devcontainer/README.md(216 lines) - Comprehensive documentation and troubleshooting guide.devcontainer/.gitattributes(2 lines) - Ensures shell scripts use Unix line endings🏗️ Complete Development Stack
The Codespaces environment provides:
Core Services
Development Tools
VS Code Extensions
Pre-configured with essential extensions:
🚀 Key Features
Automated Service Management
Port Forwarding Configuration
Pre-configured forwarding for all essential services:
Remote Debugging Support
Developer Experience
🔧 Technical Implementation
Environment Setup Process
docker-compose-examples/single-node-demo-siteSmart Configuration
.gitattributes📖 Documentation Highlights
The included README provides:
🎯 Developer Benefits
Immediate Productivity
Professional Development Workflow
Flexible Usage