Just checked in my installation of DevDesktop and found that my PHP logs are located in /Applications/DevDesktop/apache/logs/error_log.
Although it says Apache logs, PHP errors get logged there as well.
You can find the log locations via 'Preferences' => 'Logs'. DevDesktop version 2 (Apr 13, 2017).
To do this, I used dev desktop to create the site instance (instantiating the database and vhost files within Apache) than overwrote that with the install I wanted. Specifically,
I created my site instance normally, selecting "Acquia Drupal" or any of the installations when it asked me to choose a distribution.
For my site settings, I changed it from the ...
You can find DB Settings of Acquia DevDesktop locally at following location
In above path Replace YOUR_USER_NAME with apropriate user name that you login on system. This path for Windows 7.
For Mac, open Terminal. By default it opens in your user home directory (/Users/"username").
The settings you are looking for are on a file in a hidden ".acquia" folder inside your user home directory.
On a freshly open Terminal window (meaning, from your user home directory, unless you changed its settings), just do the following to list the settings ...
You don't happen to have a ~/.my.cnf file (which sets the user to root)? MySQL will read that file after the file specified by --defaults-extra-file, and "If multiple instances of a given option are found, the last instance takes precedence".
These are the commands I have executed from the terminal to update Drush.
rm -rf vendor/drush/drush
rm -rf vendor/bin/drush*
rm -rf vendor/psy
rm -rf vendor/bin/psysh
composer.phar require drush/drush:8.*
I was following Introducing Drush 8 (Composer Users Downloading Stable Versions of Drush), where the suggested command ...
Had the same problem and switched from XMail to Papercut recently:
Papercut is a simplified SMTP server designed to only receive messages (not to send them on) with a GUI on top of it allowing you to see the messages it receives. It doesn't enforce any restrictions on addresses, it just takes the message and allows you see it.
So, turn off the XMail ...
They dropped PHP 5.2 support with DevDesktop 2. It has hit EOL so you really shouldn't be developing against it.
That said, if you really want to do this, you can find old versions of DevDesktop that used PHP 5.2. I would guess you might hit problems if your end goal is to deploy to AcquiaCloud.
To fix this answer I created a new Alias called adrush which points to the Acquia DevDesktop Version.
In my .bash_profile file in my home directory I added
now when running drush commands for sites that are in my Acquia DevDesktop environment I enter adrush cc all
Drupal is a dynamic application, having an index.html file wouldn't make much sense.
There is an index.php file at the root of the install (the one you've already found). All requests are sent to that script, and the Drupal bootstrap takes over and routes them to the PHP function responsible for serving the appropriate content.
If you want to change the ...
Manually starting the MySQL server:
Viewing the log:
tail -50 /Applications/DevDesktop/mysql/data/mysql.err
If everything went right you should see the MySQL green dot in the Acquia Dev Desktop GUI.
I haven't determined the root cause of this issue, but I found a functional solution:
When I get this issue, rather than in my IDE I ssh to AC via the Acquia Dev Desktop interface (clicking the small terminal icon next to the SSH address). This runs a specific SSH connection with several options:
ssh -p 22 -i "/Users/username/.ssh/acquia_key_name" -o ...
I had this problem too with Dev Desktop 2.
It was my first time trying to pull an Acquia cloud site to local.
I generated a key, added my public key to my Acquia profile, but still kept getting Authentication errors.
What fixed it for me was...
SSH into the server (little square next to the SSH path in dev desktop), then just close it.
I was then able to ...
I found the solution, you need to search the php.ini file inside the php version folder that you are using. Open the file and search for this line:
;error_log = php_errors.log
Delete the ; to activate the error logging, then you will have:
error_log = php_errors.log
Save the file and restart your server and the file will be created in your site root ...
DevDesktop 2 now supports PHP 7.1.
Updated components in the latest version:
Added option to use PHP 7.1
MySQL Windows build) updated to 5.6
Percona (Mac build) updated to 5.6
Drush updated to 8.1.15
In addition, the feedback submission function within the app has been fixed.
Since you are using Acquia Dev Desktop on a Mac, you have access to the best Drupal tool - Drush. In a terminal, navigate to the folder containing your Drupal website and run
It will return a link to reset the password for user 1. The URL returned from the command will look something like
The Acquia documentation for Dev Desktop lists very clearly the steps that need to be taken to upgrade your Drupal install: https://docs.acquia.com/dev-desktop/upgrade.
Also, if you are a subscriber, you can open a ticket with them and they will assist you.
For the permission issue, I suggest you also try the following steps.
Take ownership of the hosts file and change the permission for it
Right click on hosts file and click “Properties”.
Switch to “Security” tab and click “Advanced” button.
Switch to “Owner” tab and click “Edit…”.
Highlight your user account or ...
Couple of things.
For Windows, the DB settings are in the dir Rupesh listed. Very similar on a Mac as well:
There is a file in this directory for each site you have installed on Dev Desktop. Do not edit this file! However you can use this file to figure out where you database is, the name, etc.
DevDestop now supports this.
Acquia Dev Desktop now provides simulated HTTPS support using a self-signed SSL certificate, which supports local testing and development of websites that rely on SSL. Learn more.
Just download a new version of DevDesktop. I'm currently on Version 2, Control panel rev: 032976b and have ...
When using Acquia and Acquia Dev Desktop the settings.php is autogenerated by Acquia. If you review that settings.php file you will noticed there are no databases credentials but instead an Acquia config file is included within a conidtional. That conditional and file are:
// Please don't edit anything between <DDSETTINGS> tags.
Use the console coming with ADD - launch the console from the ADD client. Using that console everything is correct setup. You might of course get everything to work inside your "Bash" (which it think you are using since you talk about the "which" command), but it kind of removes the whole point of using ADD - that everything is working out the box.
PS! I ...
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 ...
Same issue resolved by using https://docs.acquia.com/dev-desktop/troubleshooting
SSH key error
If, when you synchronize a website between Acquia Dev Desktop and Acquia Cloud, you experience an SSH key error, you may be able to resolve it by doing the following:
In Acquia Dev Desktop, click Acquia Dev Desktop > Preferences.
On the Settings > General tab, ...
You can't at the moment. It's in Dev Desktop's known issues
Incompatible with Drupal 8.4.0 and greater
The following issues affect attempts to use Drupal 8.4.0 and greater with Acquia Dev Desktop:
Acquia Dev Desktop includes Drush version 8.1.10, but does not include Drush version 8.1.14 (which is required by Drupal versions 8.4.0 and ...
Yes, you can install more than one Drupal site on the same computer using Acquia Dev Desktop. Check out Acquia's documentation here:
It looks to me like maybe you have specified an identical name for the local database. The error screen that you see is one that commonly appears when a new Drupal installation ...
Maestrojed's own answer identifies the settings file, and hansfn has already pointed out you may need to launch the terminal session via DevDesktop itself.
Other things you can do:
First, check drush status (which'll show if it has the correct db name)
Run drush commands with the --verbose switch, which'll show bootstrap status (but beware the bootstrap ...
Disclaimer: I work for Acquia
This library article you linked to originates from an blog post that was written 4 years ago to answer questions about deploying from Jenkins build servers, private Github repos, etc. There's nothing specific to Acquia Cloud per se and it's rather a Git strategy you need to come up with for your development needs.
Is the ...