-
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, 'standard' and 'demo' options #206
Conversation
@alxp Then, when creating a repository item, I get the following error:
|
@Natkeeran I pushed a couple of updates that were causing this white screen: First added a workaround for the Install Profile hard-coding the broker URL to the default ISLE_DC hostname. Second, there is a missing check if a taxonomy term is not set. Creating a new object now works as expected. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Built without error once I'd upgraded to current Ansible.
All derivatives were created on media ingest.
GitHub Issue: Islandora/documentation#1194
Release pull requests, etc.)
Uses install-profile branch, a D9 update, of https://github.com/Islandora-Devops/islandora-sandbox/tree/install-profile
Related PR on Islandora-Devops/islandora_install_profile_demo: Islandora-Devops/islandora_install_profile_demo#3
What does this Pull Request do?
Allows a user to run a playbook that installs either a standard Drupal distribution with Islandroa and Islandora Defaults enabled, without much more customization, or the 'demo' profile, based on the install profile provided to the community by Born DIgital and updated with Drupal 9 compatibility for this PR.
What's new?
The base install should not change - it still uses the drupal/recommended-project composer project as a base, and it is the default option for the ISLANDORA_INSTALL_PROFILE variable.
The user now has an option to set that variable to 'demo', which will check out the install-profile branch of the Islandora-Devops/islandora-sandbox project ** for now ** and run composer install when the Drupal role is executed.
THis can be a basis for Ansible to deploy an organization's own project, just by changing the drupal variables in var/demo to point to their own repo. It doesn't need to be in composer.
PR includes an update to the README. External install docs should be updated also.
If 'demo' is install, it will point to the Islandora-Devops/islandora-sandbox composer project which depends on Islandora-Devops/islandora_install_profile_demo.
(i.e. Regeneration activity, etc.)?
I faccepted, we need to decide what the branch scheme of islandora-sandbox is 'main' is still needed elsewhere in its current form.
Default is to stick with 'standard' so no.
How should this be tested?
after running vagrant destroy:
Set a Unix shell variable:
export ISLANDORA_INSTALL_PROFILE=demo
Run 'vagrant up
Interested parties
Tag (@ mention) interested parties or, if unsure, @Islandora-Devops/committers