ericas-clinic-softeo-test
This is a project that aims to help Erica in the management of her clinic. And it is also a job oportunity test from Softeo company.
Science Score: 18.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
✓CITATION.cff file
Found CITATION.cff file -
○codemeta.json file
-
○.zenodo.json file
-
○DOI references
-
○Academic links in README
-
○Academic email domains
-
○Institutional organization owner
-
○JOSS paper metadata
-
○Scientific vocabulary similarity
Low similarity (0.9%) to scientific vocabulary
Last synced: 10 months ago
·
JSON representation
·
Repository
This is a project that aims to help Erica in the management of her clinic. And it is also a job oportunity test from Softeo company.
Basic Info
- Host: GitHub
- Owner: junior8319
- Language: JavaScript
- Default Branch: main
- Size: 658 KB
Statistics
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 1
- Releases: 0
Created almost 4 years ago
· Last pushed over 3 years ago
Metadata Files
Citation
Owner
- Name: Antonio Carlos Nunes da Silva Junior
- Login: junior8319
- Kind: user
- Repositories: 6
- Profile: https://github.com/junior8319
Citation (citations.md)
De Tiago H. S. Sathler, em: Canal sd-15-tribo-b // Slack // 17/04/2022
VISIBILIDADE: a ideia deu certo! Nada demais... Apenas alguns acréscimos de scripts de execução nos dois arquivos package.json (um da pasta raiz e outro do backend) e a criação de outro arquivo de orquestração docker-compose.dev.yml, alterando a forma de subir o container do backend por VOLUMES (o requisito sugere usar Dockerfile, possivelmente - grifo - através de uma imagem buildada da API).
Pronto! Bastou executar apenas uma vez o docker-compose e visualizar os logs do container. Através deles é possível ver quaisquer alterações da API, pois o código é re-compilado imediatamente (usando nodemon). Os testes locais podem ser executados a qualquer tempo. O contêineres do frontend e db nada mudam. Você ainda poderá se conectar ao mysql dockerizado e abrir o app do frontend direto browser, como fazíamos no módulo anterior!! E o bom disso tudo é que o outro docker-compose, exigido pelo projeto, continuará funcionando normalmente no evaluator.
Importante: para tudo isso dar certo, só se pode usar o docker compose de uma solução por vez: seja pela forma como o requisito pede (imagem buildada) ou por esta abordagem em modo desenvolvimento (através de volumes). As duas soluções ao mesmo tempo vai dar ruim, porque haverá, no mínimo um conflito de portas.
Ponho-me à disposição para quaisquer esclarecimentos. Sugestões e críticas são sempre bem vindas (desde que construtivas, please.
/********************************************************/
Exemplo de docker-compose.yml de Tiago H. S. Sathler:
Projeto Trybe Futebol Clube
version: '3.9'
services:
frontend:
build: ./frontend
container_name: app_frontend
depends_on:
backend:
condition: service_healthy
healthcheck:
test: ["CMD", "lsof", "-t", "-i:3000"]
timeout: 10s
retries: 5
restart: "no"
ports:
- "3000:3000"
backend:
build: ./backend
container_name: app_backend
depends_on:
db:
condition: service_healthy
environment:
- PORT=3001
- DB_USER=root
- DB_PASS=123456
- DB_HOST=db
- DB_NAME=TRYBE_FUTEBOL_CLUBE
- DB_PORT=3306
healthcheck:
test: ["CMD", "lsof", "-t", "-i:3001"]
timeout: 10s
retries: 5
restart: "no"
ports:
- "3001:3001"
db:
image: mysql:8.0.21
container_name: db
ports:
- "3002:3306"
environment:
- MYSQL_ROOT_PASSWORD=123456
restart: 'always'
healthcheck:
test: ["CMD", "mysqladmin" ,"ping", "-h", "localhost"]
timeout: 10s
retries: 5
cap_add:
- SYS_NICE
/********************************************************/
/********************************************************/
Exemplo de docker-compose.dev.yml de Tiago H. S. Sathler:
Projeto Trybe Futebol Clube
version: '3.9'
services:
frontend:
build: ./frontend
container_name: app_frontend
depends_on:
backend:
condition: service_healthy
healthcheck:
test: ["CMD", "lsof", "-t", "-i:3000"]
timeout: 10s
retries: 5
restart: "no"
ports:
- "3000:3000"
backend:
image: node:16-alpine
container_name: app_backend
working_dir: /api
volumes:
- ./backend/:/api
command: npm install -g npm@latest
command: npm run debug
depends_on:
db:
condition: service_healthy
environment:
- PORT=3001
- DB_USER=root
- DB_PASS=123456
- DB_HOST=db
- DB_NAME=TRYBE_FUTEBOL_CLUBE
- DB_PORT=3306
- FOCE_COLOR=true
healthcheck:
test: ["CMD", "lsof", "-t", "-i:3001"]
timeout: 10s
retries: 5
restart: "no"
ports:
- "3001:3001"
db:
image: mysql:8.0.21
container_name: db
ports:
- "3002:3306"
environment:
- MYSQL_ROOT_PASSWORD=123456
restart: 'always'
healthcheck:
test: ["CMD", "mysqladmin" ,"ping", "-h", "localhost"]
timeout: 10s
retries: 5
cap_add:
- SYS_NICE
/********************************************************/
GitHub Events
Total
Last Year
Dependencies
backend/package-lock.json
npm
- 242 dependencies
backend/package.json
npm
- @tsconfig/node16 ^1.0.3 development
- @types/express ^4.17.13 development
- @types/node ^18.7.14 development
- @types/sequelize ^4.28.14 development
- nodemon ^2.0.19 development
- ts-node ^10.9.1 development
- ts-node-dev ^2.0.0 development
- typescript ^4.8.2 development
- dotenv ^16.0.2
- express ^4.18.1
- jsonwebtoken ^8.5.1
- mysql2 ^2.3.3
- sequelize ^6.21.4
- sequelize-cli ^6.4.1
frontend/package-lock.json
npm
- 1174 dependencies
frontend/package.json
npm
- @testing-library/jest-dom ^5.16.5
- @testing-library/react ^13.3.0
- @testing-library/user-event ^13.5.0
- react ^18.2.0
- react-dom ^18.2.0
- react-scripts 5.0.1
- web-vitals ^2.1.4
backend/Dockerfile
docker
- node 16-alpine build
frontend/Dockerfile
docker
- node 16-alpine build