--- title: "Resources in Cloud IDE" date: "2024-02-14T06:18:38+00:00" summary: "Explore Cloud IDE's powerful development environment with fixed resources, essential tools, and PHP extensions. Learn to manage services and customize Apache for efficient Drupal development." image: type: "page" url: "/acquia-cloud-platform/add-ons/cloud-ide/resources-cloud-ide" id: "ae45c98a-e46b-4c3d-8645-3325c245a77c" --- Table of contents will be added Each Cloud IDE provides a container with useful resources and tools to help you develop your application. Note * This page applies only to Cloud IDE. Other environments, such as [Cloud Platform](/acquia-cloud-platform/architecture/tech-platform#cloud-other-stack-info), [Pipelines](/acquia-cloud-platform/features/pipelines/container), and [Cloud Platform CD](/acquia-cloud-platform/features/cd/resource), may provide different resources. * Cloud IDE does not support memcache. Resource limits --------------- Cloud IDE containers provide fixed amounts of system resources. Resource Limit Disk space 60 GiB Memory 3 GiB CPU 1.8 cores 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: Resource Version Acquia CLI 2.60.0 Composer 2 2.9.5 Git 2.49 GitHub CLI 2.89.0 GitLab CLI 1.92.0 MariaDB (MySQL) Version Distribution 8.0.43-34 Apache2 2.4.41 PHP 8.2.30, 8.3.30, 8.4.19, 8.5.4 Xdebug 2.9.0, 3.0.2 Drush 8.5.0 Drush Launcher 0.10.2 Theia 1.70.2 Node Version Manager (NVM) 0.40.4 Node.js 22.22.2 npm 11.4.1 Google Chrome 147.0.7727.55-1 Ruby Version Manager (RVM) 1.29.12 Ruby 3.4.9 ImageMagick 6.9.10-23 ChromeDriver 147.0.7727.55 PHP extensions -------------- Cloud IDE containers provide the same PHP extensions that [Cloud Next](/acquia-cloud-platform#cloud-next-cloud-classic) 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](https://www.squiz.net/) * [PEAR](https://pear.php.net/) * [Zend](https://www.zend.com/) * [PSR2](https://www.php-fig.org/psr/psr-2/) * [PSR1](https://www.php-fig.org/psr/psr-1/) * [PSR12](https://www.php-fig.org/psr/psr-12/) * MySource * [Coder](https://www.drupal.org/project/coder/) Managing your services ---------------------- Users of Cloud IDE can manage services in the container using the following commands: Command Description `acli ide:service-start $SERVICE` Starts the service, if it wasn’t running before. `acli ide:service-stop $SERVICE` Stops the service, if it was running before. `acli ide:service-restart $SERVICE` Restarts the service. Note Cloud IDE users do not have access to the `sudo` or `root` user. 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](#ide-managing-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](#ide-managing-services) by running the following command: acli ide:service-restart apache