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.
421 İşleme
3 Dallar
268 MiB
 
 
 
 
Ağaç: d28df4b866
Dallar Biçim İmleri
${ item.name }
${ searchTerm } dalı oluştur
'd28df4b866'den
${ 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 hafta önce
..
ci initial directory layout 8 yıl önce
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 hafta önce
init-scripts feat: add alerts topic, publish alert messages to MQTT broker from the bridge 2 ay ö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 3 hafta önce
README.md build config file location clarification 7 yıl önce
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 hafta önce
docker-compose.woodpecker.yml chore: big refactoring job 4 hafta önce
docker-compose.yaml feat: add script for building the docker containers, change prod docker compose to use built images 3 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: