pollutri
/
res_levis_backend
1
0
Форкнуть 0
Код Задачи 9 Pull Request'ы 0 Релизы 0 Вики Активность
Вы не можете выбрать более 25 тем Темы должны начинаться с буквы или цифры, могут содержать дефисы(-) и должны содержать не более 35 символов.
421 коммит
3 Ветки
268 MiB
 
 
 
 
Дерево: d28df4b866
Ветки Теги
${ item.name }
Создать ветку ${ searchTerm }
из 'd28df4b866'
${ noResults }
res_levis_backend/build
Blaz Smehov d28df4b866 feat: add script for building the docker containers, change prod docker compose to use built images 3 недель назад
..
ci initial directory layout 8 лет назад
env 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 недель назад
init-scripts feat: add alerts topic, publish alert messages to MQTT broker from the bridge 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 3 недель назад
README.md build config file location clarification 7 лет назад
docker-compose.dev.yml 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 недель назад
docker-compose.woodpecker.yml chore: big refactoring job 3 недель назад
docker-compose.yaml feat: add script for building the docker containers, change prod docker compose to use built images 3 недель назад

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: