enhance(docker): template update on page refresh

[wesleyboar]

Overview

When developing locally, template edits should be reflected on page after page refresh without needing to rebuild the image, so I mount the local ./service/templates directory into the authenticator container.

Caution

This docker-compose.yml is used on production, so I must instead:

• document this as useful for dev env
• offer via docker-compose.local.py
• follow peer direction

Changes

• added ./service/templates volume mount to authenticator service in docker-compose.yml

Testing

1. Start up the app.
2. Edit a file in service/templates/
3. Refresh the browser/page.
4. Changes appear without rebuilding image.

UI

Test.Docker.Volume.Mount.of.Templates.mov

[gcurbelo123]

This alone didn't enable hot reload, I also had to add this at line 26 in models.py:
app.config['TEMPLATES_AUTO_RELOAD'] = True

[wesleyboar]

@gcurbelo123, true. I shouldn't have said "live reload". I've renamed the PR to instead describe accurately what it does. My intent was not automatic reload, but just to make page refresh result in latest template.

[wesleyboar]

@gcurbelo123, sorry. Fixed now. I misunderstood your comment as a request for auto reload on file change, but it is a bug¹ report.

Footnotes

1. File change and refresh alone, inadequate (because cache). ↩

[wesleyboar]

Important

This is used on prod. Make it dev-only.

Technically that docker-compose is used to build in jenkins. So an extra - ./service/templates:/home/tapis/service/templates could introduce out-changes we don't want if it gets built on an unclean repo. And there could be local issues if a user directly publishes.
— @NotChristianGarcia

I'm not against the dev docker-compose change. But it might be possible to add a new Makefile target called make dev or make local for the reload explicitly? The build job makes make build currently. So just something to be aware of.
— @NotChristianGarcia