Posts on Twitter:

Did I mention that had 6 more developers pass their Developers certification and 1 more site builder! That's 7 developers and 23 builders.

A comparison of the Drupal 7 and Drupal 8 content creation screen to highlight some of the improvements in Drupal 8.

Asia Pacific & Japan would like to wish you all a very happy and healthy New Year. We look forward to working with our customers, partners, employees and community of developers towards a very successful and transformational 2019!

Retweet Retweeted Like Liked

Free on-demand webinar! Catch up on 's latest updates and learn what's coming in 2019. > Acquia Platform Updates: New Features and Capabilities

Feeling some monolith migration misery? Here are some of the Acquia Professional Services team’s findings on managing a successful a migration, no matter the size.

We were at Acquia Japan’s year end partner party! Great time with APJ Chris Gibbs! Bright future ahead 2019 for management in Japan market!

アクイアジャパン設立プレスリリースを配信した昨日、いつもお世話になっているパートナー様をお招きした「アクイアジャパン Year-End Party」を開催いたしました。 これからもパートナー様とともに日本市場を盛り上げていきたいと思いますので、引き続きよろしくお願いします! 

Go zero to in 60 days. Join CTO Dries Buytaert to discover why is the best content management foundation for developers and digital experience builders:

Hosting over a hundred Product Managers at tonight’s evening event at !

Hosting over a hundred Product Managers at tonight’s evening event at !

Posts on Tumblr:

The Open Source Report 09 December 2018

thanks Acquia

for all those times i’ve been really thankful for varnish caching on our staging servers.

External image

Acquia Dev Cloud Gotchas

The Acuia Dev Cloud is a great service for hosting Drupal sites, giving you Drupal specific management stuff via the GUI and turning many of the standard workflow tasks from CLI to GUI. Unfortunately, the docs and support are a little scant as they are still being developed and can leave you feeling pretty isolated if you get a problem. Being propitiatory, the systems and techniques are not widely known and not much community stuff is out there. Here are a few of the main gotchas that I found moving from a standard Drupal infrastructure (e.g. Dedicated server, VPS or shared server) to the Dev Cloud. They may be obvious to some but maybe will help others.

  1. The Acquia file directory structure is a little different and what would normal be your Dupalroot is now docroot, this all within the sites root along with a couple of other Acquia specific folders.
  2. Your files directory is stored in a different location automagically on Acquias network when you import your site. It is then symlinked to you standard drupal_root/sites/[site]/files directory. To upload new files you must scp or sftp them - uri’s can be found under sites & logs. So if you use git like me, you will find an entry excluding files within .gitignore stopping them being added to your repo.
  3. Only tags & branches show in the code drop down list on the workflow page NOT commits when pushing code to the dev cloud from your local environment. This means that if you want to commit a change to the Dev Cloud and want to see that change by checking out code to your Workflow dev site for example, you need to use 'git tag mytweak' followed by ‘git push –tags’ to get the tag to show in the code drop down.

As I find more things worth noting I’ll post 'em.