Closed mheadd closed 4 years ago
Here's an oddball idea. Stay at the current version while you're making the example more usable. Then tag the easier-to-use-but-still-outdated Drupal as, say, drupal8-example-before-update
. Then do your updates.
Now you can have that as a resource for the question: "How do I update Drupal on cloud.gov" with something like:
Updating drupal takes the following X steps, and you can try it our yourself with:
git co drupal8-example-before-update
- then do x, y, z, and you'll see you have a fully patched drupal install.
If you update the Drupal version before you've made it easier to use then you miss out on this training/demo opportunity.
So I hear what you are saying... the problem is updating from this version to the current version requires several annoying steps in addition to the normal composer update drupal/core-recommended --with-dependencies
I am happy to include all of the various steps, but this update to current version (8.9.^) is going to be a different pathway than updating if on anything above 8.8^
Where we are in this repo for the updates IS the pain point. Pathauto complains when you update straight to the recommended version of core, and it is a known issue skipping from 8.7 pathauto version to 8.8+ pathauto version....
I guess I will note all of the steps + how to update going forward and update the readme.
Thanks for the clarification! I hope things get easier once you get past the 8.8 hurdle. Nevermind my comment. --Peter
On Fri, Jun 12, 2020 at 9:35 AM Becca notifications@github.com wrote:
So I hear what you are saying... the problem is updating from this version to the current version requires several annoying steps in addition to the normal composer update drupal/core-recommended --with-dependencies
I am happy to include all of the various steps, but this update to current version (8.9.^) is going to be a different pathway than updating if on anything above 8.8^
Where we are in this repo for the updates IS the pain point. Pathauto complains when you update straight to the recommended version of core, and it is a known issue skipping from 8.7 pathauto version to 8.8+ pathauto version....
I guess I will note all of the steps + how to update going forward and update the readme.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/cloud-gov/cf-ex-drupal8/issues/50#issuecomment-643273565, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJHWCTENXAZM6637IIBLR3RWIVH7ANCNFSM4N3TLXPA .
Peter Burkholder cloud.gov compliance & security | co-lead DevOps Community of Practice https://digital.gov/communities/devops/
Solutions https://www.gsa.gov/about-us/organization/federal-acquisition-service/technology-transformation-services/tts-solutions | Technology Transformation Services https://join.tts.gsa.gov/tts-offices/
|
GSA http://www.gsa.gov/portal/category/100000
202-709-2028 <(202)%20209-2028> | peter.burkholder@gsa.gov peter.burkholder@gsa.gov
| pronouns he-him https://www.mypronouns.org/he-him Free/Busy Calendar https://calendar.google.com/calendar/embed?src=peter.burkholder@gsa.gov
Closing in favor of #51 and #52. /cc @onelittlebecca
In order to support customers that want to run Drupal on the cloud.gov platform, we want to provide an updated example install and documentation for how to manage and update.
Acceptance Criteria
Security considerations
Implementation sketch