Static Docker production deployment? #9

New Issue

2021-04-24T19:45:10Z

3wordchant commented

2021-04-24 19:45:10 +00:00

Currently the approach to serving files is to define a prod script for npm which runs elm-live, run it as the Docker CMD, and port-forward to that from Traefik.

This seems like kind of a waste of resources and an excessive attack surface. We should just be able to run npm build and then wrap up the public directory into an appropriately-configured Nginx container – but I need to get my head around Docker builds a bit more to work out how this should happen most efficiently.

Currently the approach to serving files is to [define a `prod` script for `npm` which runs `elm-live`](https://git.autonomic.zone/coop-cloud/abra-apps/src/branch/main/package.json#L8), [run it as the Docker `CMD`](https://git.autonomic.zone/coop-cloud/abra-apps/src/branch/main/Dockerfile#L15), and [port-forward to that from Traefik](https://git.autonomic.zone/coop-cloud/abra-apps/src/branch/main/compose.yml#L21). This seems like kind of a waste of resources and an excessive attack surface. We should just be able to run `npm build` and then wrap up the `public` directory into an appropriately-configured Nginx container – but I need to get my head around Docker builds a bit more to work out how this should happen most efficiently.

3wordchant added the enhancement question labels 2021-04-24 19:45:10 +00:00

3wordchant referenced this issue from a commit

2023-01-23 04:42:42 +00:00

Switch to static deployment

3wordchant closed this issue

2023-01-23 04:42:43 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: toolshed/recipes.coopcloud.tech#9