To create, delete, list or open Cloud IDE, you must install Acquia CLI.
When managing your Cloud Platform organization’s roles, you can configure two permissions:
Yes, you can use any Git repository such as GitHub, Bitbucket, or GitLab. You must install an SSH key in the Acquia Cloud IDE that has permissions to access the external repository.
Cloud IDE fully supports Drupal multisite applications, whether they’re hosted
on the Cloud Platform or Site Factory. When running the acli pull
command,
you can select any arbitrary database or files directory to pull from.
Since Cloud IDE only has one preview URL, a limitation is that you can only run one application at a time.
Acquia doesn’t officially support this use case yet. Hence, you might experience issues when developing headless/decoupled applications with Drupal’s JSON:API and REST clients. The issue might arise while trying to use the preview site as Acquia doesn’t strip the share parameter before proxying the request onto the IDE.
MySQL data is available under /home/ide/mysql-data
.
By design, Cloud IDE pulls the latest daily MySQL backup. We have on our roadmap to provide an option to Acquia CLI so it can create an on-demand backup to pull into the IDE.
The Drupal watchdog log is available under /var/log/drupal/drupal-watchdog.log
.
Read our documentation about it
for more information.
If you configure the Cloud Platform pipelines feature to work with your Git repository, all Git pushes to the repository, or pull requests (PRs) opened from your external provider, will trigger a pipelines job.
Important
EOL notice! Acquia will no longer provide updates or support for Dev Desktop after June 30, 2021. Acquia recommends transitioning to the use of Acquia Cloud IDE for a managed development environment on Acquia Cloud Platform. To learn more, see Migrating from Dev Desktop to Cloud IDE.
Cloud IDE and Acquia Dev Desktop are separate products. Acquia Dev Desktop runs a LAMP stack locally on your computer to develop Drupal. Cloud IDE is a cloud-hosted, browser-based development environment and source code editor for Drupal which simplifies Drupal development and integration with Cloud Platform applications.
After Drupal is installed, the settings.php
file gets write-protected. On
the Acquia Cloud Platform, this is not an issue as the filesystem is
read-only. However, in Acquia Cloud IDE, as you can edit files, you might run
into this issue.
To make Drupal’s settings.php
writable, run the following command from
within the project
directory:
ide:~/project $ chmod 644 docroot/sites/[yoursite]/settings.php
Once your changes are made, run the following command to make the file write-protected again:
ide:~/project $ chmod 444 docroot/sites/[yoursite]/settings.php
While trying to delete files or directories in the Drupal docroot, you might
get the following Permission denied
messages:
ide:~$ rm -Rf project
rm: cannot remove 'project/docroot/sites/default/files': Permission denied
rm: cannot remove 'project/docroot/sites/default/default.settings.php': Permission denied
rm: cannot remove 'project/docroot/sites/default/settings.php': Permission denied
rm: cannot remove 'project/docroot/sites/default/default.services.yml': Permission denied
The above issue is related to Drupal permissions. Before you can delete those files or directories, you must change permissions.
To do so, run the following command:
chmod -R u+w /home/ide/project/docroot/sites/default
You can now delete those files and directories.
You might have a contributed or custom module that causes a redirect loop. Here’s a list of contributed modules that can cause this issue:
Your .htaccess
file might be configured in a way that is incompatible with
Cloud IDE. See Excluding Acquia domains and non-production environments and redirecting visitor requests with the .htaccess file.
One of the first things new Acquia customers ask our Support team is how to disable Varnish in non-production Cloud Platform environments, so that they can view their changes immediately. Taking this feedback into account, we’ve decided not to include Varnish in Acquia Cloud IDE so it’s easier to develop Drupal without any external caching in the way.
It is useful to understand who created or deleted an IDE. To
achieve this, use Acquia CLI, as Acquia CLI
lets you filter out your Cloud Platform notifications easisly. Ensure that
you adjust the --limit
parameter to make it relevant. The rule of thumb
is: the more you have Cloud Platform notifications, the more you’ll have to
increase the limit.
$ acli api:applications:notification-list myapplication --limit=100 | grep -B2 -A1 IDE
"uuid": "2b328ed0-74be-413d-a3f9-d19c74a96239",
"event": "RemoteIdeCreatedEvent",
"label": "IDE created",
"description": "IDE \"Mary\" created for \"My Application\".",
"created_at": "2021-03-15T13:35:21+00:00",
--
"uuid": "p14300b9-cf78-46b6-bh3a-005d73bc6836",
"event": "RemoteIdeDeletedEvent",
"label": "IDE removed",
"description": "IDE removed from \"My Application\".",
"created_at": "2021-03-12T20:58:32+00:00",
Follow the procedure to Add a shortcut to a website as an app.
When prompted to create the shortcut, make sure to check the Open as window
check box. To locate your application, visit chrome://apps/
in your browser.