pollutri
/
res_levis_backend
1
0
Derivar 0
Código Questões 9 Pedidos de integração 0 Lançamentos 0 Wiki Trabalho
Não pode escolher mais do que 25 tópicos Os tópicos devem começar com uma letra ou um número, podem incluir traços ('-') e podem ter até 35 caracteres.
456 Cometimentos
3 Ramos
491 MiB
 
 
 
 
Ramo: master
Ramos Etiquetas
${ item.name }
Criar ramo ${ searchTerm }
de 'master'
${ noResults }
res_levis_backend/build
Blaz Smehov 4892be4ff9 fix: add restart policy to the docker compose há 1 semana
..
ci initial directory layout há 8 anos
env feat: change message retention há 1 mês
init-scripts fix: add missing kafka topics to init script há 2 semanas
package feat: add switching between ml and filter algorithm, various fixes in context use, script for creating docker images, various bug fixes regarding persistence in db, persisting alerts in db and CRUD operations for alerts há 2 meses
README.md build config file location clarification há 7 anos
docker-compose.db.yml chore: several fixes, including token, kafka backoff, timeouts, using context with timeout, adding volumes to postgres and kafka, scripts for creating and restoring sql dump há 2 meses
docker-compose.dev.yml chore: log cleanup há 1 semana
docker-compose.local.yml fix: add restart policy to the docker compose há 1 semana
docker-compose.yaml chore: log cleanup há 1 semana

README.md

/build

Packaging and Continuous Integration.

Put your cloud (AMI), container (Docker), OS (deb, rpm, pkg) package configurations and scripts in the /build/package directory.

Put your CI (travis, circle, drone) configurations and scripts in the /build/ci directory. Note that some of the CI tools (e.g., Travis CI) are very picky about the location of their config files. Try putting the config files in the /build/ci directory linking them to the location where the CI tools expect them when possible (don’t worry if it’s not and if keeping those files in the root directory makes your life easier :-)).

Examples: