A devops engineer should be able to add services to the project without confusion
Purpose: PythonDocker is currently most useful as a quick means of building our backend image, but it's over-referencing in the code base makes it seem more confusing/used than it really is.
Description
The process of making a basic django backend
- adding poetry to a base python image
- installing an application (and its dependencies)
- setting an entrypoint
doesn't require creativity, and is therefore automated in PythonDocker. However, adding a "black box" to the code base should both only be done as necessary and be done as little as necessary. This issue sets to clarify what PythonDocker is used for, and to remove unnecessary references to it.
Functionality: This will remove unnecessary refs to PythonDocker, and add a bit of documentation about what it does.
Affects: Reduce bloat (and hopefully confusion)
Additional context
Add any other context or screenshots about the feature request here.
Requires #15
A devops engineer should be able to add services to the project without confusion
Purpose: PythonDocker is currently most useful as a quick means of building our backend image, but it's over-referencing in the code base makes it seem more confusing/used than it really is.
Description
The process of making a basic django backend
doesn't require creativity, and is therefore automated in PythonDocker. However, adding a "black box" to the code base should both only be done as necessary and be done as little as necessary. This issue sets to clarify what PythonDocker is used for, and to remove unnecessary references to it.
Functionality: This will remove unnecessary refs to PythonDocker, and add a bit of documentation about what it does.
Affects: Reduce bloat (and hopefully confusion)
Additional context
Add any other context or screenshots about the feature request here.