Workspace Types

When creating a workspace, you select a workspace type that determines the runtime environment, pre-installed tools, and shell configuration for your development workflow.

Available Types

Type	Use Cases	Runtime
PHP-Based	Magento 2, Laravel, Shopware, etc.	PHP-FPM + Composer
NodeJS	Next.js, Nuxt, Express, headless frontends	Node.js + npm/yarn/pnpm

Note

PHP-based applications appear as separate workspace types in the creation wizard (e.g., “Magento 2”, “Shopware”, “Laravel”) because each requires a different web server configuration. They share the same shell environment and tooling.

How Workspace Types Differ

The primary difference between workspace types is how the web server (Nginx/Apache) is configured to serve your application:

• PHP types — The web server is configured to invoke PHP-FPM for request processing. Different PHP frameworks require different web server rules (e.g., Magento 2 and Shopware each need distinct Nginx/Apache configurations for URL rewrites, static asset handling, and entry points).
• NodeJS types — The web server acts as a reverse proxy, forwarding HTTP traffic to the port where your Node application is listening.

Beyond the web server configuration, each workspace type also provides:

• Runtime environment — Language version, package manager, and process manager
• Shell environment — Pre-configured $PATH, aliases, and helper commands
• CLI tools — Framework-specific commands available in your shell

Selecting a Workspace Type

The workspace type is chosen during workspace creation in the Basic Configuration step. It cannot be changed after creation — to switch types, create a new workspace.

Tip

If your project uses both PHP and Node (e.g., a Magento 2 storefront with a Node-based build pipeline), choose the PHP workspace type. Node.js is available in PHP workspaces for asset compilation.