-
Notifications
You must be signed in to change notification settings - Fork 62
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
Cert issue in Lando local environment #355
Comments
Thanks for the report, @cjcodes. For the public record, I've worked around this issue (error posting schema) by copying the schema.xml file to the correct place on the filesystem. For me, this is It looks like Lando is defining the |
We may want to come to a consensus with the Lando team about how best to handle this. Ideally we can supply a slug of configuration that will make it work with their local environment without any hacking needed. |
@danielbachhuber Indeed copying the schema.xml helps, but there are two other issues I've run into:
@joshkoenig I'll hold on any PRs then until I hear from you--I'm happy to code up the solution by detecting |
Revisiting this. I'm running a a local Lando environment with the default I did not run into any cert issues. Perhaps this was fixed in a future configuration of the |
When developing locally with Lando, the certs required for this plugin to work are not installed.
Temporarily, I had to comment out:
includes/class-pantheoncurl.php:27
includes/includes/class-solrpower-api.php:109
includes/includes/class-solrpower-api.php:118
(Line numbers come from the latest version released on wp.org.)
I don't yet have recommended solution steps (in crunch mode on a project), but want to create a placeholder issue or perhaps one of y'all has a good quick solution.
Alternatively, we could look into moving this issue over into the Lando repo to have certs included there, but I think it's a solvable problem on this side. (The certs are installed to /certs in the Docker container, but it's called "index.pem," not "binding.pem".)
The text was updated successfully, but these errors were encountered: