Contributes to # (add issue number here. i.e. #302)
What did you do?
Added a set of files to make use of a local development environment in a Docker container. This will be useful for lab environments where we present Legit Info as the demonstration application, such as in the Call for Code Roadshow events.
Why did you do it?
As we were building the prerequisites for Call for Code Comes to You material, we realized that it might be more difficult for folks to get their machines setup. We opted to add these files to build a local development environment with Docker to simplify this process. These files should not affect the application itself.
How have you tested it?
We built the files and tested them across Windows, Linux, and macOS.
Were docs updated if needed?
[x] No
[ ] Yes
[ ] N/A
Type of change
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
Checklist:
[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
Contributes to # (add issue number here. i.e.
#302)What did you do?
Added a set of files to make use of a local development environment in a Docker container. This will be useful for lab environments where we present Legit Info as the demonstration application, such as in the Call for Code Roadshow events.
Why did you do it?
As we were building the prerequisites for Call for Code Comes to You material, we realized that it might be more difficult for folks to get their machines setup. We opted to add these files to build a local development environment with Docker to simplify this process. These files should not affect the application itself.
How have you tested it?
We built the files and tested them across Windows, Linux, and macOS.
Were docs updated if needed?
Type of change
Checklist: