Each Cloud IDE provides a container with useful resources and tools to help you develop your application.

Resource limits

Cloud IDE containers provide fixed amounts of system resources.

These limits cannot be changed and apply to all processes running inside the IDE, including the Drupal database, Drupal code, Drupal files, and IDE frontend.

Tools

Cloud IDE containers provide standard Ubuntu tooling and the following development tools:

PHP extensions

Cloud IDE containers provide the same PHP extensions that Cloud Next provides.

Theia plugins

Cloud IDE provides Theia plugins that can be configured using the options provided in ~/.theia/settings.json.

For example, the PHP_CodeSniffer (phpcs) plugin provides the following configuration options:

• phpcs.enable: Enables and disables the phpcs extension. The default value is true.
• phpcs.standard: Stores the phpcs coding standard. The default value is Drupal. Other available options:
  • Squiz
  • PEAR
  • Zend
  • PSR2
  • PSR1
  • PSR12
  • MySource
  • Coder

Managing your services

Users of Cloud IDE can manage services in the container using the following commands:

Apache web server resources

Apache and PHP are enabled in your container. Your container serves files from the /home/ide/project/docroot directory. The Apache access logs are present in /var/log/apache2/. The PHP error logs are present in /var/log/php/.

Although users can install packages, change system settings, and restart services, these changes aren’t guaranteed to persist.

Altering Apache configuration

To change default options in Apache or create new virtual hosts, you can create and change files in the /home/ide/configs/apache2/ directory. After creating or modifying any Apache configuration file, you must restart the apache2 service by running the following command:

acli ide:service-restart apache

Resources in Cloud IDE

acli ide:service-restart apache