PHP-Based Workspace Types

Several workspace types are available for PHP applications — including Magento 2, Laravel, Shopware, and others. These appear as distinct types in the workspace creation wizard because each requires a different web server configuration (URL rewrites, entry points, static asset handling). However, they all share the same underlying shell environment and tooling described below.

Web Server Configuration

The web server (Nginx or Apache) is configured to pass requests to PHP-FPM for processing. Each workspace type has server rules tailored to its framework’s routing and directory structure. Selecting the correct type ensures the web server handles your application’s URLs properly.

Shell Environment

When you SSH into a PHP workspace, the following tools and paths are pre-configured:

PHP CLI

# Check PHP version
php -v

# Run a PHP script
php script.php

# Check loaded modules
php -m

The PHP version matches what was selected during workspace creation. Multiple versions are not available simultaneously — the configured version is the one used by both the CLI and the web server.

Composer

Multiple Composer versions are installed side-by-side. The workspace’s configured default version is symlinked as composer, but you can invoke any specific version directly:

# Use the configured default
composer install

# Use a specific version explicitly
composer1 install        # Composer 1.x
composer2 install        # Latest Composer 2.x
composer2.2 install      # Composer 2.2.x
composer2.3 install      # Composer 2.3.x
composer2.7 install      # Composer 2.7.x

Available binaries: composer1, composer2, composer2.1, composer2.2, composer2.3, composer2.4, composer2.5, composer2.6, composer2.7, composer2.8, composer2.9.

Tip

The default version is set via the workspace configuration (defaults to 2 if not specified). If your project requires a specific Composer version, you can run it directly without changing the workspace config.

Node.js (Asset Compilation)

Node.js and npm are available in PHP workspaces for frontend asset builds:

node -v
npm -v

# Install frontend dependencies
npm install

# Run build scripts
npm run build

Pre-Installed CLI Tools

Beyond PHP and Composer, the following tools are available out of the box:

Tool	Command	Purpose
WP-CLI	wp	WordPress management
n98-magerun	n98-magerun	Magento 1 CLI utility
n98-magerun2	n98-magerun2	Magento 2 CLI utility
Shopware CLI	shopware-cli	Shopware development CLI
AWS CLI	aws	AWS service management
Kiro CLI	kiro	AI-assisted development
MySQL client	mysql	Database access
PostgreSQL client	psql	Database access
MongoDB Shell	mongosh	MongoDB access
Git	git	Version control
jq	jq	JSON processing
rsync	rsync	File synchronization

Framework-Specific Usage

Magento 2 / Adobe Commerce

# Navigate to project root
cd /home/web/html

# Run Magento CLI
php bin/magento setup:upgrade
php bin/magento setup:di:compile
php bin/magento setup:static-content:deploy -f
php bin/magento cache:flush

# Reindex
php bin/magento indexer:reindex

# Check module status
php bin/magento module:status

Database access:

mysql -h db -u root -p $WORKSPACE_DB_NAME

Redis (if enabled):

redis-cli ping
redis-cli flushall

Elasticsearch / OpenSearch:

# Check cluster health
curl http://db:9200/_cluster/health

# List indices
curl http://db:9200/_cat/indices?v

Laravel

cd /home/web/html

# Artisan commands
php artisan migrate
php artisan cache:clear
php artisan config:cache
php artisan queue:work

# Run tests
php artisan test

Shopware

cd /home/web/html

# Shopware CLI
php bin/console cache:clear
php bin/console plugin:refresh
php bin/console plugin:install PluginName
php bin/console plugin:activate PluginName
php bin/console dal:refresh:index
php bin/console theme:compile

# Shopware CLI tool
shopware-cli project ci

WordPress

cd /home/web/html

# WP-CLI commands
wp core version
wp plugin list
wp plugin update --all
wp theme activate theme-name
wp cache flush
wp search-replace 'old-url.com' 'new-url.com'
wp db export backup.sql

Clean Install

When creating a workspace, you can choose Clean Install to automatically install a fresh copy of your application. The wizard presents version options specific to each workspace type.

Default Admin Credentials

Platform	Username	Password
Magento 2 / Adobe Commerce	admin	Ordin@Dev1
WordPress	admin	Ordin@Dev1
Shopware	admin	shopware

Caution

Change the default admin password after installation if the workspace is accessible beyond your team.

Magento 2 / Adobe Commerce

Available versions: 2.4.6, 2.4.7, 2.4.8, 2.4.9 (both Enterprise and Open-Source editions).

The clean install process:

1. Runs composer create-project from the Magento repository
2. Executes bin/magento setup:install with database, search engine, and URL configuration
3. Runs indexer:reindex
4. Sets developer mode
5. Symlinks pub/ to the web root

Requirements: An auth.json file must exist in /shared/ with your Magento repository credentials. Place it there before creating the workspace.

Shopware

Available versions: 6.5, 6.6, 6.7.

The clean install process:

1. Runs composer create-project shopware/production
2. Installs dev tools
3. Configures .env.local with database, OpenSearch, and URL settings
4. Runs bin/console system:install --basic-setup
5. Indexes with OpenSearch
6. Symlinks public/ to the web root

WordPress

Available versions: latest, 6.6, 6.7.

The clean install process:

1. Downloads WordPress core via wp core download
2. Creates wp-config.php with database credentials
3. Runs wp core install with site URL and admin credentials

Environment Variables

Ordin automatically injects environment variables into the workspace to pass configuration values to your application. These are set by the platform based on your workspace and project settings — you don’t manage them directly.

Commonly used variables:

Variable	Example	Description
WORKSPACE_DOMAIN_1	mysite.project.ordinlabs.io	Primary workspace URL
WORKSPACE_DB_HOST	db	Database hostname
WORKSPACE_DB_NAME	workspace_abc	Database name
WORKSPACE_DB_USER	root	Database user
WORKSPACE_DB_PASSWORD	(set automatically)	Database password
WORKSPACE_NAME	mysite	Workspace subdomain

Your application code and config templates can reference these to connect to services without hardcoding values. See Workspace Config Templates for the full list.

Common Tasks

Testing HTTP Output

curl -H "Host: $WORKSPACE_DOMAIN_1" http://localhost

Checking Logs

# PHP-FPM error log
tail -f /var/log/php-fpm/error.log

# Web server access/error logs
tail -f /var/log/nginx/error.log
tail -f /var/log/apache2/error.log

Cron Jobs

Cron is managed by the workspace. To run a cron command manually:

# Magento cron
php bin/magento cron:run

# Laravel scheduler
php artisan schedule:run

File Structure

/home/web/
├── html/              # Web root (application code)
│   ├── composer.json
│   ├── pub/           # Magento public directory
│   └── ...
├── .bashrc            # Personal shell config
└── .workspacerc       # Workspace-specific config

/shared/               # Shared across project workspaces
├── .profile           # Project-wide shell profile
├── .bashrc            # Project-wide bash config
├── bin/               # Shared scripts (in $PATH)
└── startup.d/         # Scripts run on environment start