yasithdev opened a new pull request, #113: URL: https://github.com/apache/airavata-portals/pull/113
Second step of extracting Wagtail out of `airavata-django-portal`: stand up a new, **independent** Wagtail **7.4** / Django **6.0** (Python 3.13) project, `airavata-cms`, that will own the gateway's admin-authored content (landing pages, documentation sites). It is decoupled from the portal — the portal stays a stateless gateway UI with no CMS/DB, and a reverse-proxy router will later stitch the two into one site (portal serves the app paths; this CMS serves the content paths). This PR is the **scaffold only**: the canonical `wagtail start` layout (the `airavata_cms` project with split base/dev/production settings, a `home` page app, the search view, a production Dockerfile, pinned requirements) plus `.gitignore` and `README`. It migrates cleanly and `manage.py check` passes on sqlite (validated on Python 3.13). Follow-ups in this track: port the existing portal page models (`HomePage`/`BlankPage`/`CybergatewayHomePage`) and the seagrid theme/fixtures into this service, add the reverse-proxy router, then remove Wagtail from the portal. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
