pollutri
/
res_levis_backend
1
0
Çatalla 0
Kod Konular 9 Değişiklik İstekleri 0 Sürümler 0 Wiki Aktivite
25'ten fazla konu seçemezsiniz Konular bir harf veya rakamla başlamalı, kısa çizgiler ('-') içerebilir ve en fazla 35 karakter uzunluğunda olabilir.
456 İşleme
3 Dallar
491 MiB
 
 
 
 
Dal: master
Dallar Biçim İmleri
${ item.name }
${ searchTerm } dalı oluştur
'master'den
${ noResults }
res_levis_backend/build
Blaz Smehov 4892be4ff9 fix: add restart policy to the docker compose 1 hafta önce
..
ci initial directory layout 8 yıl önce
env feat: change message retention 1 ay önce
init-scripts fix: add missing kafka topics to init script 2 hafta önce
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 ay önce
README.md build config file location clarification 7 yıl önce
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 ay önce
docker-compose.dev.yml chore: log cleanup 1 hafta önce
docker-compose.local.yml fix: add restart policy to the docker compose 1 hafta önce
docker-compose.yaml chore: log cleanup 1 hafta önce

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: