Skip to content
This repository has been archived by the owner on Feb 27, 2024. It is now read-only.

Commit

Permalink
Add details on where to run some commands.
Browse files Browse the repository at this point in the history
  • Loading branch information
tharna committed Oct 12, 2017
1 parent 0a5e0a3 commit a49abf7
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions troubleshooting.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ Make sure you have provisioned all environment variables.
`./provision.sh -t drush,drupal-db,php-fpm <env>.yml`

* #### Drush doesn't work, cant connect to db or see any environment variables ####
See previous question to ensure your environment variables are provisioned.
See previous question to ensure your environment variables are provisioned. This also seems to affect drush9.
If your project is using drush-launcher that doesn't use global drushrc.php anymore. You need to have project specific drushrc.php in place that includes the global one.
Create file called `drushrc.php` under `drupal/drush` with the following content:
```
Expand All @@ -20,7 +20,7 @@ require '/etc/drush/drushrc.php'

* #### Varnish repo is outdated ####
Symptom: provision fails
Old official repo.varnish-cache.org repo is deprecated. This might lead to existing environments provisioning to fail even as we have already fixed the issue in the wundermachina. The fix is to ensure the target environment doesn't have reference to the old repo anymore by either running `sudo yum-config-manager --disable varnish-4.1` or manually removing the `/etc/yum.repos.d/varnish.repo` and reprovisioning varnish again (`./provision.sh -t varnish [env]`)
Old official repo.varnish-cache.org repo is deprecated. This might lead to existing environments provisioning to fail even as we have already fixed the issue in the wundermachina. The fix is to ensure the target environment doesn't have reference to the old repo anymore by either running `sudo yum-config-manager --disable varnish-4.1` or manually removing the `/etc/yum.repos.d/varnish.repo` from inside the box and then reprovisioning varnish again (running `./provision.sh -t varnish vagrant` from the host)


* #### key.wunder.io issues ####
Expand Down

0 comments on commit a49abf7

Please sign in to comment.