Task/fp 1499 cms pattern library - serve at /ui url

[wesleyboar]

Overview

Serve TACC/Core-CMS#512 taccsite_ui/ at /ui.

Related

• FP-1499
• supports task/FP-1499: CMS pattern library Core-CMS#512

Changes

• (docker-compose) mount taccsite_ui/ at cms/ui
• (nginx) serve cms/ui at /ui

Testing / UI

See TACC/Core-CMS#512 for remote servers.

[codecov]

Codecov Report

Merging #677 (0b2e884) into main (8efdf57) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #677   +/-   ##
=======================================
  Coverage   67.35%   67.35%           
=======================================
  Files         429      429           
  Lines       13422    13422           
  Branches     2500     2500           
=======================================
  Hits         9040     9040           
  Misses       4090     4090           
  Partials      292      292           

Flag	Coverage Δ
javascript	69.01% <ø> (ø)
unittests	66.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

[wesleyboar]

This solution would only let me serve the files locally. The changes here have no effect on remote server.

I will use this to test Nginx syntax and PoC locally. But a new plan is required to serve on a remote server.

Details

S.T.
4 minutes ago
So the nginx file in the core-portal repo is only used locally. Deployed environments use camino

S.T.
4 minutes ago
Extended by core-portal-deployments

S.T.
4 minutes ago
Check out how the user guide is served for frontera prod

S.T.
4 minutes ago
I imagine a similar setup for these staticfiles

W.B.
🧠 4 minutes ago
Ah, okay. Yeah, I started [by emulating] the docs and Core-Portal-Deployments. (edited)

W.B.
🧠 4 minutes ago
I’ll return to that solution. (edited)

S.T.
2 minutes ago
A key part of that solution is that bringing the docs container “up” results in the container placing the staticfiles directly on a mounted volume. This lets nginx see those files

S.T.
2 minutes ago
Alternatively you could use a similar “running” container solution like how certain nginx locations point to either the cms or portal containers