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

Consider setting projectPath based on .git directory if one exists #52

Open
danielbachhuber opened this issue Jun 1, 2023 · 1 comment

Comments

@danielbachhuber
Copy link
Member

If I run wp-now start anywhere from a git clone, I may want it to reuse the same WordPress instance.

We could consider looking upwards for a .git directory, and use that as the projectPath if it exists.

From #39 (comment)
Related #26

@danielbachhuber danielbachhuber changed the title Consider setting projectPath based on .git directory if one exists Consider setting projectPath based on .git directory if one exists Jun 1, 2023
@lemanschik
Copy link

while i like the pattern to search for a .git directory this does not scale well we need a
wp-now.config.json inside the project directory or alternative for vscode inside the .vscode project folder.

The most standard scenario is the one where we even need more then a single wp-now deployment to migrate data and settings and maybe even work with a directory that has many wp installations.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants