pollutri
/
res_levis_backend
1
0
Çatalla 0
Kod Konular 1 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.
415 İşleme
3 Dallar
9.8 MiB
 
 
 
 
Dal: master
Dallar Biçim İmleri
${ item.name }
${ searchTerm } dalı oluştur
'master'den
${ noResults }
res_levis_backend/build
Blaz Smehov f27512f183 feat: add api endpoint for parser registry CRUD operations 2 hafta önce
..
ci initial directory layout 8 yıl önce
init-scripts feat: add alerts topic, publish alert messages to MQTT broker from the bridge 1 ay önce
package feat: add api endpoint for parser registry CRUD operations 2 hafta önce
README.md build config file location clarification 6 yıl önce
docker-compose.dev.yml chore: update docker compose, dockerfile of decoder to copy the decoding config, add open api schema for beacon parser 3 hafta önce
docker-compose.yaml chore: update docker compose, dockerfile of decoder to copy the decoding config, add open api schema for beacon parser 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: