Add --port option to run-webapp. #667

telackey · 2023-11-28T07:34:19Z

telackey commented

2023-11-28 07:34:19 +00:00

Short of a full deployment, being able to specify the port can still be useful (eg, in scripting).

❯ laconic-so run-webapp --image cerc/test-progressive-web-app:local --port 4243
Image: cerc/test-progressive-web-app:local
ID: c6642396ebc339f2f4f6fca4ff353e67214002370228a5b4aad08b47cdd6b4e7
URL: http://localhost:4243

Short of a full deployment, being able to specify the port can still be useful (eg, in scripting). ``` ❯ laconic-so run-webapp --image cerc/test-progressive-web-app:local --port 4243 Image: cerc/test-progressive-web-app:local ID: c6642396ebc339f2f4f6fca4ff353e67214002370228a5b4aad08b47cdd6b4e7 URL: http://localhost:4243 ```

dboreham commented

2023-11-28 16:39:54 +00:00

This maps the container port to some specified port on the host, presumably?

telackey commented

2023-11-28 18:33:01 +00:00

Yep, rather than using a random port. The idea was that if you had a proxy in front (nginx, for example) it would be a configuration hassle if the container if the port changed every time.

dboreham approved these changes 2023-11-28 19:02:08 +00:00

dboreham referenced this issue from a commit

2024-02-08 19:44:23 +00:00

Add --port option to run-webapp. (#667)

Sign in to join this conversation.

No reviewers

No Milestone

No project

No Assignees

2 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cerc-io/stack-orchestrator#667