-
Notifications
You must be signed in to change notification settings - Fork 53
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
Install profile #200
Install profile #200
Conversation
Giving this a go right now. |
Failed on the JWT config import:
It is complaining that Bartik won't be installed but we have bartik related configs. Perhaps we need to move the bartik configs to a |
Forgot to push a stray commit. This just enabled Bartik without setting it as the default. I noticed that the config items that referenced Bartik are already in /optional so not sure what's going on there. |
Ran it again and hit an error with migrations where it couldn't connect to activemq:
I'm going to destroy the box and try again. |
Found the problem. Following the threads lead me to the activemq config @ https://github.com/Islandora-Devops/islandora_install_profile_demo/blob/main/config/install/islandora.settings.yml#L1, which I presume was set to use an activemq host name for Docker. But we aren't using Docker for the playbook so Drupal can't find the host "activemq". The playbook needs this config to be 'tcp://localhost:61613' or 'tcp://127.0.0.1:61613'. |
Perhaps the install profile needs to have both a Docker and a Playbook branch? Tagging @dannylamb. |
I think a separate local settings module that adds e.g. docker-specific settings that gets installed after the profile would make sense.
… On May 5, 2021, at 8:10 PM, Seth Shaw ***@***.***> wrote:
Perhaps the install profile needs to have both a Docker and a Playbook branch?
Tagging @dannylamb <https://github.com/dannylamb>.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#200 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAUD3HFPOGUQXHO2QXSFFDTMHF7TANCNFSM434OAP6A>.
|
Updated to support multiple install profiles. See the 'how should this be tested' section or the updated README. |
GitHub Issue: Make Islandora a Drupal Distribution
What does this Pull Request do?
Uses a composer project to set up a Drupal project, which then imports an install profile that can be set in a variable. Available profiles are the standard profile and the Born Digital-derived install profile.
What's new?
Uses a composer profile that supports 3rd-party libraries and install profiles, which the Drupal recommended-project does not. Retrieves and installs a Drupal install profile specified in a Vagrant or Ansible variable.
Composer then recursively fetches the Install Profile and all requirements, so those are no longer listed in the playbook.
possible side effects.
All new install profile with modules and theme, so new sites will be fully different in look and feel and behaviour.
How should this be tested?
Before running a playbook, set the following variables in your Unix shell or Vagrantfile
ISLANDORA_DRUPAL_PROFILE_PROJECT to either islandora/islandora_profile:1.x-dev or islandora/islandora_install_profile_demo:dev-main
ISLANDORA_DRUPAL_PROFILE to either islandora_profile or islandora_install_profile_demo
Test by running a playbook install and creating nodes and media to ensure that the site behaves as expected. Some forms will be different as they have been altered by Born Digital.
Interested parties
Tag (@ mention) interested parties or, if unsure, @Islandora-Devops/committers