Environment Setup
Before customizing Aletyx Playground, ensure you have:- Docker and Docker Compose installed
- Git installed
- Access to a container registry (if deploying to Kubernetes/OpenShift)
- Basic understanding of environment variables and container concepts
Basic Customization
Branding
Aletyx Playground supports complete branding customization, allowing you to replace the default logos with your organization’s own branding.Logo Customization
You can replace the following files in the container image:Favicon is an
.svg not a .icoExample Dockerfile for Branding
Application Name
You can change the application name displayed throughout the UI using an environment variable:Container-Based Deployment
The easiest way to set up a customized Aletyx Playground is using Docker Compose:- Create a directory for your customization project:
- Create a
docker-compose.ymlfile (see the Docker Compose Example section) - Create a
Dockerfilefor your customizations (see the Containerfile/Dockerfile Example section) - Create a
brandingdirectory with your custom logos - Start the environment:
Advanced Customization
Services Configuration
Aletyx Playground relies on two additional services for full functionality:- Extended Services: Provides validation and runtime capabilities for your models
- CORS Proxy: Facilitates communication with external Git providers
Git Provider Integration
Aletyx Playground can integrate with various Git providers. Configure them using theKIE_SANDBOX_AUTH_PROVIDERS environment variable:
GitHub Enterprise Integration
For GitHub Enterprise instances, add a custom provider:Accelerators
Accelerators allow you to quickly bootstrap projects with predefined configurations. Configure accelerators using theKIE_SANDBOX_ACCELERATORS environment variable. For more information on Accelerators see the Accelerators and Accelerators Advanced in the documentation on how to build them. To incorporate these into your build you will customize like the example:
Accelerator Structure
Each accelerator is a Git repository containing:- Project structure (src directories, pom.xml, etc.)
- Configuration files
- Deployment scripts
- README and documentation
- name: Display name shown in the UI
- iconUrl: URL to an icon image (displayed in the UI)
- gitRepositoryUrl: URL to the Git repository
- gitRepositoryGitRef: Branch, tag, or commit to use
- dmnDestinationFolder: Where DMN files should be placed
- bpmnDestinationFolder: Where BPMN files should be placed
- otherFilesDestinationFolder: Where other files should be placed
Custom Commit Messages
You can enforce custom commit messages and validate them against your organization’s standards:Commit Message Validation Service
If you implement a validation service, it should:- Accept POST requests with the commit message in the body
- Return JSON with:
result: Boolean (true for valid, false for invalid)reasons: Array of strings explaining validation failures
Editors Configuration
You can enable or disable specific editors using theKIE_SANDBOX_EDITORS environment variable:
Docker Compose Example
Here’s a complete Docker Compose example with all customization options:Containerfile/Dockerfile Example
Troubleshooting
Common issues and solutions:Service Connectivity
If Aletyx Playground cannot connect to Extended Services or CORS Proxy:- Check that the services are running:
- Verify network connectivity:
- Check service logs:
Git Provider Authentication
If authentication with Git providers fails:- Verify CORS Proxy is running correctly
- Check the browser console for CORS-related errors
- Ensure the Git provider configuration is correct in
KIE_SANDBOX_AUTH_PROVIDERS
Accelerator Issues
If accelerators don’t appear or fail to apply:- Verify the Git repository URLs are accessible
- Check the correct branch/tag is specified in
gitRepositoryGitRef - Ensure the JSON syntax in
KIE_SANDBOX_ACCELERATORSis valid
Browser Cache Issues
If changes don’t appear after updating the container:- Clear browser cache
- Try incognito/private browsing mode
- Rebuild and restart the container: