-
Notifications
You must be signed in to change notification settings - Fork 114
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
Example wanted: Post Solr schema after creating new multidev env with Drupal #142
Comments
Seems Gizra hits again. I now also have this requirement :) @DavidHernandez did you find a solution for this? |
I see there is no way of hooking into it, but on my Site install script I could run a a similar script to do it |
I'm not sure that you can manually bootstrap from a Quicksilver script. Try using |
Hi @greg-1-anderson 😄 I think there are two cases here. One that is for new multi-dev, where Solr is already assumed to be enabled (David's scenario) And the other is upon spinning a new site (my scenario). So in my case, I probably wouldn't want a hook, since it's not guaranteed Solr is already enabled.
Can you please clarify where to place the exec -- I didn't get this part. |
Yes, I was only addressing the My suggestion was to make your quicksilver hook run a script via Drush:
Then, in private/scripts/my_post_schema.php:
Disclaimer: Untested. I suspect, but do not guarentee that the above should work. Some assembly (or debugging) required. |
Related to #62, we tried to implement the "autoposting" solr schema using the
create_cloud_development_environment
event with no luck.On our pantheon.yml file we have this:
Then, we have the configure_solr.php file, that contains the next code:
But this code is not working and I can not figure out why. Also, I tried to debug it following the steps mentioned in the troubleshooting part of the quicksilver documentation, it says to use
terminus workflow:list
to get the logs. I just created a new multidev environment and it does not even appear on the list of workflows, so is not possible to get the logs.The text was updated successfully, but these errors were encountered: