yasithdev opened a new pull request, #115:
URL: https://github.com/apache/airavata-portals/pull/115

   ## A4 — remove Wagtail from the portal; route CMS content to the standalone 
service
   
   With the standalone **airavata-cms** Wagtail service now owning landing 
pages, documentation, and other editable content (#114), the portal no longer 
needs an embedded CMS. This removes Wagtail from the portal entirely and adds 
the reverse-proxy routing that sends content paths to the CMS — one coherent 
decoupling change.
   
   ### Removed
   - **`settings.py`** — the `wagtail.*` apps, `modelcluster`/`taggit`, the 
three wagtail third-party apps, and `django_airavata.wagtailapps`; 
`RedirectMiddleware`; the `WAGTAIL_*` / `WAGTAIL_CODE_BLOCK_*` settings (the 
language list alone was ~200 lines). 662 → 429 lines.
   - **`urls.py`** — the `/cms` (Wagtail admin), `/documents`, and root 
catch-all (`wagtail_urls`) routes + their imports. Unmatched paths now fall 
through to the proxy → CMS.
   - **`django_airavata/wagtailapps/`** — the whole package (models, snippets, 
blocks, migrations, fixtures, management commands, tests) and every Wagtail 
template (`wagtail_base.html`, the CMS-page includes, `blocks/`, `tags/`).
   - **deps + build** — `wagtail`, `wagtailfontawesome`, 
`wagtail-draftail-anchors`, `wagtailcodeblock` from 
`requirements.txt`/`setup.py`; the now-dead `cms` webpack entry and `js/cms.js`.
   
   ### Added
   - **`deploy/reverse-proxy.conf`** (nginx) + **`deploy/README.md`** — the 
routing contract: the portal's app path prefixes (`/workspace`, `/auth`, 
`/api`, `/admin`, …) go to the portal; everything else goes to airavata-cms. 
The README documents the CMS-side prefix contract (`/cms-static`, `/cms-media`, 
`/cms` admin) so its assets don't collide with the portal's 
`/static`/`/media`/`/admin`.
   
   ### Net effect
   **123 files, +69 / −83,386.** `manage.py check` passes. The portal app shell 
(decoupled from Wagtail in #112) is unaffected — it sources its chrome from 
`settings.PORTAL_CHROME`.
   
   ### Depends on
   The standalone CMS (#114) being the new home for this content. This PR is 
code-independent of #114 (portal-only changes + a deploy contract) and can be 
reviewed in parallel; they should land together so content is served 
continuously.


-- 
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]

Reply via email to