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.
371 İşleme
3 Dallar
9.3 MiB
 
 
 
 
Ağaç: e14d8e0d97
Dallar Biçim İmleri
${ item.name }
${ searchTerm } dalı oluştur
'e14d8e0d97'den
${ noResults }
res_levis_backend/build
Blaz Smehov 6db62dde15 feat: reimplement redis support, using hash maps for quick insert and read 1 hafta önce
..
ci initial directory layout 8 yıl önce
init-scripts feat: locations algorithm, chore: remove unused files 1 hafta önce
package chore: add health check for EMQX, bridge service awaits check 1 ay önce
README.md build config file location clarification 6 yıl önce
docker-compose.yaml feat: reimplement redis support, using hash maps for quick insert and read 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: