ejmg
commented
4 years ago We have discussed this a few times during our post-class team meetings.
DigitOcean remains our most likeliest hosting service to put up the web application and database itself; PostgreSQL remains our choice for if a fully fledged database is seen as necessary for full feature delivery with respect to data permanence and scheduling logic.
Docker will be carried as a dev environment tool and possibly into production if possible, at least for CI/CD purposes.
Given some complications experienced by @ArcTangent20EggsEggs, we are going to move forward with a rust prototype for now instead of python. I'll be handling it from here for the foreseeable future. Our technical stack will reflect this, but is liable to change.
Technical Stack
For this project, we need to resolve around a common technical stack to begin delivering our project.
Assignees
Everyone
Background
Our team has a mixed technical background. During our first meeting, we discussed possible languages such as:
What matters more than anything is choosing one (or two) of these to figure out how to proceed with the feature set for iteration 1 and each onwards.
Furthermore, it would probably be ideal to figure out a common development and production environment. This may mean using tools like such as:
figuring out where/how we test development and where it gets thrown for deployment testing matters as much as the language choice.
Constraints and Assumptions
Other than the experience of each team member and how that may influence their ability to use the tools selected, there are no constraints or assumptions at play here.
Blockers
None
Design Changes
This is the beginning of the design for this project.
References
None