feat: Multi-stage build Dockerfile for building and serving threat composer. Close #97 #128
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ode from checkout and subsequently copies the website folder into a second stage image that runs the website via nginx
jessieweiyi
changed the title
jessieweiyi
approved these changes
Aug 8, 2024
|
Next step will be:
|
|
🎉 This PR is included in version 1.0.55 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…ode from checkout and subsequently copies the website folder into a second stage image that runs the website via nginx
Issue #97 :
Description of changes:
Adds a two-stage docker container that builds a container to build the code and run the application containerized. The container uses the aws-pdk container image to build the first stage and the alpine-nginx to serve the application.
Note that serving happens by default on 80. We assume that the image is run locally over a laptop. If additional SSL/TLS implementation is required it must be done by the user at the loadbalancer level.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.