Skip to main content
Aletyx Playground can be fully customized to meet your organization’s branding, security, and development needs. This guide covers all aspects of Aletyx Playground customization, from simple branding changes to advanced features like custom accelerators and authentication providers.

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 .ico

Example 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:
  1. Create a directory for your customization project:
  1. Create a docker-compose.yml file (see the Docker Compose Example section)
  2. Create a Dockerfile for your customizations (see the Containerfile/Dockerfile Example section)
  3. Create a branding directory with your custom logos
  4. Start the environment:

Advanced Customization

Services Configuration

Aletyx Playground relies on two additional services for full functionality:
  1. Extended Services: Provides validation and runtime capabilities for your models
  2. CORS Proxy: Facilitates communication with external Git providers
Configure these services using environment variables:

Git Provider Integration

Aletyx Playground can integrate with various Git providers. Configure them using the KIE_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 the KIE_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
Each accelerator definition requires:
  • 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:
  1. Accept POST requests with the commit message in the body
  2. Return JSON with:
  3. result: Boolean (true for valid, false for invalid)
  4. reasons: Array of strings explaining validation failures
Example response for an invalid message:

Editors Configuration

You can enable or disable specific editors using the KIE_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:
  1. Check that the services are running:
  1. Verify network connectivity:
  1. Check service logs:

Git Provider Authentication

If authentication with Git providers fails:
  1. Verify CORS Proxy is running correctly
  2. Check the browser console for CORS-related errors
  3. Ensure the Git provider configuration is correct in KIE_SANDBOX_AUTH_PROVIDERS

Accelerator Issues

If accelerators don’t appear or fail to apply:
  1. Verify the Git repository URLs are accessible
  2. Check the correct branch/tag is specified in gitRepositoryGitRef
  3. Ensure the JSON syntax in KIE_SANDBOX_ACCELERATORS is valid

Browser Cache Issues

If changes don’t appear after updating the container:
  1. Clear browser cache
  2. Try incognito/private browsing mode
  3. Rebuild and restart the container: