Yes I tried that multiple times… Problem is, I’m not running the site with Caddy, but under Apache. Reverse proxying to the nginx server in docker, which is not treating the MFE_HOST (apps.{lms domain}) URL. Please see my first post for details.
I see also in the logs (after tutor local quickstart) that the MFE stuff is being built and copied on deployment (webpack runs, zillions of npm packages are installed, etc. etc), also there’s a running docker container “tutor_local_mfe_1”.
And I even could login to it (docker exec -it tutor_local_mfe_1 ash), and see there a Caddyfile that makes appearantly caddy listening to port 8002.
What I don’t see anywhere in the nginx docker container (tutor_local_nginx_1), is some kind of proxying to this MFE caddy instance.
As I wrote above, I’m reverse proxying to the nginx instance, but maybe must I proxy all “apps.domain-redacted.com” queries to localhost:8002 ?? I don’t see that port exposed either in the docker status:
CONTAINER ID IMAGE
56d37e4b480bc.... docker.io/overhangio/openedx-mfe:12.0.0
COMMAND
"caddy run --config /etc/caddy/Caddyfile --adapter caddyfile"
CREATED STATUS PORTS
2 days ago Up 27 hours 80/tcp, 443/tcp, 2019/tcp
NAMES
tutor_local_mfe_1
My actual config.yml looks like (all keys etc removed):
CMS_HOST: studio.domain-redacted.com
ENABLE_HTTPS: true
ID: enkHCttn1YGeR1sLphOLXfwk
LANGUAGE_CODE: es-419
LMS_HOST: domain-redacted.com
MFE_HOST: apps.domain-redacted.com
PLUGINS:
- android
- disallow_account_creation
- discovery
- ecommerce
- license
- mfe
- minio
- notes
- xqueue
RUN_CADDY: false
RUN_SMPT: true
Obs.: The parameter “MFE_HOST” I had to add manually on upgrade from koa, as not even “tutor plugin activate mfe” adds this parameter to config.yml.
What I suppose is lacking (with RUN_CADDY: false) is, a link between the MFE instance and the nginx instance inside nginx config, so URL’s starting with “http://apps.domain-redacted.com” are forwarded correctly to this MFE instance.