pollutri
/
res_levis_backend
1
0
Fork 0
Código Issues 9 Pull requests 0 Versões 0 Wiki Atividade
Você não pode selecionar mais de 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.
435 Commits
3 Branches
268 MiB
 
 
 
 
Tag: 536c959d76
Branches Tags
${ item.name }
Criar branch ${ searchTerm }
de 536c959d76
${ noResults }
res_levis_backend/build
Blaz Smehov 04574f16d8 feat: change message retention 1 semana atrás
..
ci initial directory layout 8 anos atrás
env feat: change message retention 1 semana atrás
init-scripts feat: change message retention 1 semana atrás
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 3 semanas atrás
README.md build config file location clarification 7 anos atrás
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 2 semanas atrás
docker-compose.dev.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 2 semanas atrás
docker-compose.woodpecker.yml chore: big refactoring job 3 semanas atrás
docker-compose.yaml 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 2 semanas atrás

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: