Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Take correct action on custom commands if project not running, fixes #1716 #1744

Merged
merged 3 commits into from
Jul 31, 2019

Conversation

rfay
Copy link
Member

@rfay rfay commented Jul 30, 2019

The Problem/Issue/Bug:

#1716 points out that custom command handling when the project is not running is really ugly; it tries to take action, but finds no container to execute in.

How this PR Solves The Problem:

  • For both host and container commands, if the project is not running, start it.

Manual Testing Instructions:

  • ddev mysql with project stopped.
  • Enable the host-side phpstorm command by cd .ddev/commands/host && ln -s phpstorm.example phpstorm and ddev phpstorm. It should start the project first. mysqlworkbench is more fun with this, because it actually wants the mysqlserver running, but it runs on the host.

Automated Testing Overview:

  • No changes, it seems this is really just finesse.

Related Issue Link(s):

Release/Deployment notes:

@rfay rfay added this to the v1.10 milestone Jul 30, 2019
@rfay rfay force-pushed the 20190730_custom_command_not_running branch from 3d03829 to 738dce9 Compare July 30, 2019 18:05
@rfay rfay merged commit ab3de84 into ddev:master Jul 31, 2019
@rfay rfay deleted the 20190730_custom_command_not_running branch July 31, 2019 11:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant