Motivation

Leverage the latest release. Atm the demo is using Drupal 10.3 still.

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

fago created an issue. See original summary.

roderik’s picture

"example" MR is was for a live demo of Gitlab live editing - nothing to see there.

You know this, but just documenting after I did a test update: the upgrade of lupus-decoupled-project still needs D11 compatibility of

Also, the lupus_decoupled_drupal_example module included in the repo needs D11 compatibility.

fago’s picture

Version: 1.0.0-rc2 » 1.x-dev
useernamee’s picture

Status: Active » Needs review

I created a PR: https://github.com/drunomics/lupus-decoupled-project/pull/6

Sadly, this upgrade brings breaking changes (it requires a manual step for existing projects) to the project due to the necessary mariadb upgrade from 10.3 to 10.6. I had to start ddev with old version of mariadb and afterwards run ddev debug migrate-database mariadb:10.6 to get everything up and running.

roderik changed the visibility of the branch 3477949-example to hidden.

roderik’s picture

Thank you. I re-tested for your remark and think this is fine (commented why in the github PR). So I felt confident enough to merge it.

I tested the gitpod link on the project page, and it starts Drupal 11 now.

This means this issue is done, right? Just doublechecking...

---

The frontend home URL for the gitpod demo stll starts with a single "home" link (referring to itself), no link to log in, and only a message

You are not authorized to access this page.

This is what I have gotten used to, on my local dev environment, and I didn't know whether it was just my local install...

But I guess the followup to do something about it, is #3473237: Add Login link toggle to demo frontend...

useernamee’s picture

Well maybe I should add upgrade path into the readme somewhere (set mariadb to 10.3 in ddev config, ddev start and then ddev debug migrate-database mariadb:10.6 ).

roderik’s picture

That's what I initially thought and why I tested. But since I saw that DDEV actually says this by itself, I personally don't think it's really necessary.

roderik’s picture

Oops: I was too quick. Just discovered that the project type needs to be updated too. See https://github.com/drunomics/lupus-decoupled-project/pull/7 (as yet unmerged).

fago’s picture

Status: Needs review » Fixed

I merged this and fixed the gitpod setup to work gain, thus closing.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.