# Plando app - devops, week 2

###### tags: `Report` `1st-Month` `Migration` `Go` `Mongodb` `Plando`
:::info
:calendar: **Period:** 16th to 20th of march.
:::
## :memo: Planned

### 1: Informations needed

- [ ] dns administrator
- [x] frontend full start
- [x] dotenv file

I have missed the dotenv file to be able to see the actual state of the database.
Also I need to know where our dns are being handled, for future network planning.

I need help with the frontend part of the project. Because we need to make sure that the `front->api->db` is working as expected to finish the development enviroment setup.

### 2: Proposal for week
In last week task I have discovered the non existence of migration tools. This has to be fixed even before we have a frontend container setup. Because of it I put the database deploy(migrations tools) before the docker image for frontend. And our tests setup after that.

- [x] database deploy
- [x] seed commands
- [x] migration commands
- [x] scripts
- [x] automation
- [x] docker image for frontend
- [ ] ~~tests setup~~
- [ ] ~~unit node~~
- [ ] ~~integration node~~
- [ ] ~~e2e node~~

## Reunions
This week I can see two importants meeting topics, the **database evolutionary view point** and the **changes made on the crud api for the contaninerization**.

- [Frontend startup] with Gui: 18/03 1h.
- [DB evolution and isolation by services contracts] with Gui: 20/03 30min.

## Delivered

- [PR with migrations on **plando-infra**](https://github.com/LucasBadico/plando-infra/pull/1)
- [PR with automation of migrations on **plando-infra**](https://github.com/edwardvdk/plando-infra/pull/2)
- [PR with automation of migrations on **plando-crud-api**](https://github.com/edwardvdk/nodejs/pull/3)
- [PR with dockerization of **plando-frontend**](https://github.com/edwardvdk/plando/pull/6)

## Timesheet

- [summary](https://drive.google.com/file/d/1PxXAw0JsiGpadTh7go2-7oDuxBelNpQW/view?usp=sharing)
- [detailed](https://drive.google.com/file/d/1JNdAawF9aH4ypSzSjRoHEEcnLcBZY7lu/view?usp=sharing)