6

With Acquia Cloud API v1 Drush commands On Acquia Could API v1 the command is ac-domain-purge. Here is a snippet from the drush help available from the Acquia box. $ drush help ac-domain-purge Purge a domain from the Varnish cache. Arguments: domain Domain name. Options: --username Acquia Cloud API username ...


5

You can read up on some drush specific tasks that you can do in this Elevated Third blog post Acquia supplies drush commands and aliases that tie into Acquia Cloud API calls. So you can actually simply use the alias and the rsync drush command: drush rsync --progress @sitename.env:%files @localenv:%files You can also create and download Acquia database ...


3

The body contains tokens set when you press an embed button in ckeditor. This raw body content is processed by this filter: http://cgit.drupalcode.org/entity_embed/tree/src/Plugin/Filter/EntityEmbedFilter.php public function process($text, $langcode) { $result = new FilterProcessResult($text); if (strpos($text, 'data-entity-type') !== FALSE &...


3

Acquia Cloud provides you with a default .gitignore in your repository (as described here): docroot/files docroot/sites/*/files docroot/sites/*/private acquia-files It usually is enough for the vast majority. You're however free to add anything you don't wish to keep under version control. There's no perfect setup and it really depends on what you'd like ...


2

Definitely possible and it's what I do. Acquia provides some documentation on this. As Kevin mentioned you can do this by setting up two remotes for your local repository clone, one at GitHub/GitLab/Bitbucket, and one at Acquia Cloud.


2

There is also a module for that called appropriately "Acquia Purge". Works perfectly. Details from project page: The Acquia Purge module allows Drupal sites hosted on Acquia Cloud to automatically purge (wipe) pages from their Varnish powered load balancers, as soon as content actually changed. The higher Drupal's "expiration of cached pages"-setting (TTL)...


2

Implement a directory redirect on your local environment's web server so that any request for /files/* gets redirected to /sites/default/files/* For example in Apache, edit the httpd-vhosts.conf <VirtualHost *> ServerName yourservername DocumentRoot "pathtoyourdocroot" Redirect /files /sites/default/files </VirtualHost>


2

Working on the frontend isn't tied to using Acquia Dev Desktop or not. It's a personal preference to work locally by cloning a remote site and work on theming/frontend and commit changes periodically to the remote repo when you're happy with the changes you see in your browser. Some customers prefer working directly on the Acquia Cloud dev environment with ...


2

Acquia works on a three-environment system. When working in such a system, code moves up, from dev -> stage -> prod, while databases move down from prod -> stage -> dev. You should always consider content on dev and stage, such as nodes, users, taxonomies etc, as temporary. This is because the way to migrate content is by migrating the entire database from ...


2

When you create a block using views you can add it to the page through the interface. Go to, admin/structure/block and find the region you want to add the block to, then click place block. Now find your block in the list and configure it to only show on the specefic page. There are some tabs where you can configure where the block is shown, then tell it to ...


1

Acquia has to have the full site, core, modules, themes, libraries, et.al. checked into their git repo in the format like: git root docroot core modules themes etc. (includes index.php and other root files) As Clive said, there is a pay for it CI process. However, for the normal sites, you need to manage the site as a whole entity. ...


1

The commit message isn't passed in to the script, so you have to get it from somewhere else. I'm not sure if there is a git repository available to the cloud hook scripts on Acquia's cloud servers in general (it seems like there must be, but...I can't find an answer about where it is in their docs). You do have the repository url and the branch/tag, so you ...


1

The data-entity-type & data-entity-uuid properties are added with WYSIWYG fields when you have the Track images uploaded via a Text Editor filter . This filter is designed to track usage of images as they are dropped into HTML body fields and update the fields accordingly when the image is updated. To disable it, navigate to the Text formats and ...


1

The solution was to forget about Acquia and start using cPanel. In here, was as straightforward as creating a subdomain, taking advantage of Softaculous scripts by installing in that location the 8.4.3 version of Drupal. Once installation was complete (which was a matter of seconds) and I've logged in as admin, installing a module was never easier! See ...


1

Correction : The install of Backup And Migrate works. Follow the procedure explained before to enable ssh access. Once logged in, do cd ~/dev/livedev/docroot Then drush -y en backup_migrate That's all. I tried. It just works. Here is screenshot :


1

The best is enable your access to the command line to their server. For this you need to store your public ssh_key in your profile on their platform. Then to find the exact server and username to connect do : Sign in to the Acquia Cloud interface. Select your application and environment. In the menu to the left, click Users and Keys, to see your exact ...


1

The right command is: curl https://ftp.drupal.org/files/projects/admin_toolbar-8.x-1.14.tar.gz | tar xz f process a file, but you want to process the standard input (provided by curl). So remove the f and add the x option to uncompress file. Anyway I think is better to use Drush. Drush can handle dependencies (it can download dependant modules when you ...


1

I use the combo of BitBucket/JIRA. There are many people that like GitHub's issue tracker too. Acquia has tutorial on setting up either service as a 2nd remote repo. Either service will give you a way to track issues against your commits.


1

Check the size of the files, maybe they are to big. Check the max. file sizes on your server and in Drupal!. PHP configuration check: check the following parameters: post_max_size upload_max_filesize If these values are to small, you have to change them on your server in your PHP configuration (for example php.ini)


1

Short answer: turn off livedev in your Acquia Cloud dev environment. Longer Answer: I was trying to drush my modules and do basic site building in their environment using the livedev option. But they don't let you run mkdir and scp live in their environment via CLI. Their recommended workflow will have you add your modules/libraries locally, commit via git ...


Only top voted, non community-wiki answers of a minimum length are eligible