pollutri
/
res_levis_backend
1
0
Forkuj 0
Kod Zgłoszenia 9 Oczekujące zmiany 0 Wydania 0 Wiki Aktywność
Nie możesz wybrać więcej, niż 25 tematów Tematy muszą się zaczynać od litery lub cyfry, mogą zawierać myślniki ('-') i mogą mieć do 35 znaków.
455 Commity
3 Gałęzie
491 MiB
 
 
 
 
Drzewo: d0157ce6ae
Gałęzie Tagi
${ item.name }
Utwórz gałąź ${ searchTerm }
z 'd0157ce6ae'
${ noResults }
res_levis_backend/build
Blaz Smehov 4892be4ff9 fix: add restart policy to the docker compose 1 tydzień temu
..
ci initial directory layout 8 lat temu
env feat: change message retention 1 miesiąc temu
init-scripts fix: add missing kafka topics to init script 2 tygodni temu
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 miesięcy temu
README.md build config file location clarification 7 lat temu
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 miesięcy temu
docker-compose.dev.yml chore: log cleanup 1 tydzień temu
docker-compose.local.yml fix: add restart policy to the docker compose 1 tydzień temu
docker-compose.yaml chore: log cleanup 1 tydzień temu

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: