You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: README.md
+9-3
Original file line number
Diff line number
Diff line change
@@ -248,13 +248,15 @@ P.S.: if you are interested in modifying the code as you desire, it's better to
248
248
249
249
4. (OPTIONAL) Use the script included within the **data** folder to download both datasets (one for testing and the other for training and verifying the model). You can run that from your study environment as well.
250
250
251
-
5. Use the following command to install the pre-commit package manager:
251
+
5. In order to save both Dockerfiles (for the development and production environments) in Docker Hub, you need to set up your `DOCKERHUB_USERNAME` and `DOCKERHUB_TOKEN` secrets in the repository's settings (`Settings > Secrets and Variables > Actions`).
252
+
253
+
6. Use the following command to install the pre-commit package manager:
252
254
253
255
```bash
254
256
pip install pre-commit
255
257
```
256
258
257
-
6. Activate pre-commit using the following command:
259
+
7. Activate pre-commit using the following command:
258
260
259
261
```bash
260
262
pre-commit install
@@ -309,6 +311,10 @@ docker compose up -d --no-deps --build test
309
311
310
312
12. It should take a few seconds for the tests to complete. After that, you can run `docker logs <TEST_CONTAINER_ID>` to see the overall results or view the test coverage by looking at the `cov_html` folder inside the `reports` folder.
311
313
314
+
13. The docker's GitHub action/workflow will save both Dockerfiles (one for the develop/research environment and the other for the production environmet) images in your DockerHub's profile, as illustrated in the figure below.
315
+
316
+

317
+
312
318
DISCLAIMER: Just the workflow in the research environment was tested with AWS because of financial constraints. Docker Compose should be used to run everything locally in order to fully experience both research and production workflows.
313
319
314
320
<palign="right">(<ahref="#readme-top">back to top</a>)</p>
@@ -317,7 +323,7 @@ DISCLAIMER: Just the workflow in the research environment was tested with AWS be
317
323
## Roadmap
318
324
319
325
-[ ] Add end-to-end test cases.
320
-
-[] Add a Continuous Delivery (CD) GitHub Action.
326
+
-[X] Add a Continuous Delivery (CD) GitHub Action.
321
327
-[ ] Add a integration test case to assure that the model's performance showed in MLflow is the same when evaluating the model on the same data, but using the API's code.
322
328
-[ ] Integrate uvicorn to FastAPI.
323
329
-[ ] Fix the test GitHub's workflow (it's not finishing because needs connection with FastAPI and MLflow to validate some tests).
0 commit comments