-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dockerize the development environment #17
Comments
@specious Hi Ildar! I'm Daniel's cousin, John. I have done and currently do a lot of docker containerization for my work, and I can probably provide some help with this issue. Is there a high-level overview of what the current development environment is as well as a little bit of clarification on what specifically needs to be dockerized (backend dev, frontend dev, both, etc.) that you could point me to or provide me with? Any insight you can provide as well to what can or needs to be mocked, versus what currently has a test version of the DB, etc. I'll take a look at the readme (it's pretty thorough and I haven't had time tonight), but I'd like to pitch in! |
I think the task is to manually set up the development environment and then see how it might be possible to set that functionality up in a docker container. Currently, the only dockerized workflow component is the environment for building lambda functions written in C++. |
The question of how to create a local testing environment is still an open issue: #14 |
Dockerize the development environment so that it:
The goal is to have a docker configuration so that developers run (ideally specific versions, but optionally the latest versions) of all the tools that constitute the development environment and all of this runs in a reproducible isolated docker container.
The result will be that developers won't need to install anything on their system (other than docker).
The text was updated successfully, but these errors were encountered: