pollutri
/
res_levis_backend
1
0
Форкнуть 0
Код Задачи 9 Pull Request'ы 0 Релизы 0 Вики Активность
Вы не можете выбрать более 25 тем Темы должны начинаться с буквы или цифры, могут содержать дефисы(-) и должны содержать не более 35 символов.
445 коммитов
3 Ветки
491 MiB
 
 
 
 
Дерево: 4892be4ff9
Ветки Теги
${ item.name }
Создать ветку ${ searchTerm }
из '4892be4ff9'
${ noResults }
res_levis_backend/build
Blaz Smehov 4892be4ff9 fix: add restart policy to the docker compose 1 неделю назад
..
ci initial directory layout 8 лет назад
env feat: change message retention 1 месяц назад
init-scripts fix: add missing kafka topics to init script 2 недель назад
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 2 месяцев назад
README.md build config file location clarification 7 лет назад
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 месяцев назад
docker-compose.dev.yml chore: log cleanup 1 неделю назад
docker-compose.local.yml fix: add restart policy to the docker compose 1 неделю назад
docker-compose.yaml chore: log cleanup 1 неделю назад

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: