FlexLab (Full Development Workflow)
FlexLab Installation (Developer Environment)
Overview
The FlexLab Installation is FlexSite’s developer-focused Drupal setup.
It provides a fully code-driven Drupal environment with a pre-created Git repository and automated deployments. Every site comes ready for modern development workflows, allowing teams to build, test, and ship Drupal using branches and environments.
FlexLab is designed for projects where code matters.
Who is this for?
This installation is ideal for:
- Drupal developers
- Engineering teams
- Agencies delivering custom Drupal solutions
- Projects requiring custom modules or themes
- Teams working with Git-based workflows
If your Drupal project lives in code, FlexLab is for you.
What does FlexLab provide?
FlexLab gives you:
Pre-created Git repository
Each site includes a managed repository with:
- Drupal core
- Project scaffolding
- Composer configuration
- Deployment configuration
You clone it and start coding immediately.
Automated deployments
Deployments happen automatically when code is pushed:
- No manual servers
- No SSH
- No custom pipelines required
FlexSite handles:
- Builds
- Infrastructure
- Containers
- Database connections
- File storage
Typical workflow
- Create a new site in FlexSite
- Choose FlexLab Installation
- Clone the provided Git repository
- Create a feature branch
- Push your changes
- FlexSite deploys automatically
Your branch becomes a live environment.
What’s included?
Your FlexLab site comes with:
Drupal development stack
- Drupal core
- Composer
- Custom modules support
- Custom themes support
- Configuration management
Platform features
- Multiple environments
- Branch deployments
- Automated builds
- Backups
- Security updates
- Performance tuning
What makes FlexLab different from Codeless?
| Feature | Codeless | FlexLab |
|---|---|---|
| Git access | ❌ | ✅ |
| Custom code | ❌ | ✅ |
| Branch environments | ❌ | ✅ |
| Composer | ❌ | ✅ |
| UI-only site building | ✅ | ❌ |
| Dev workflows | ❌ | ✅ |
When should I use FlexLab?
- You need custom modules or themes
- You want CI-style workflows
- You rely on Git for collaboration
- You deploy via branches
- You have developers on the project