pollutri
/
res_levis_backend
1
0
Forkuj 0
Kod Zgłoszenia 1 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.
396 Commity
3 Gałęzie
9.8 MiB
 
 
 
 
Drzewo: d977fa9175
Gałęzie Tagi
${ item.name }
Utwórz gałąź ${ searchTerm }
z 'd977fa9175'
${ noResults }
res_levis_backend/build
Blaz Smehov 1afa01b5c5 feat: add alerts topic, publish alert messages to MQTT broker from the bridge 1 miesiąc temu
..
ci initial directory layout 8 lat temu
init-scripts feat: add alerts topic, publish alert messages to MQTT broker from the bridge 1 miesiąc temu
package chore: remove unused files, add dev docker compose and dockerfile for live rebuilds and testing 1 miesiąc temu
README.md build config file location clarification 6 lat temu
docker-compose.prod.yaml chore: remove unused files, add dev docker compose and dockerfile for live rebuilds and testing 1 miesiąc temu
docker-compose.yml chore: remove unused files, add dev docker compose and dockerfile for live rebuilds and testing 1 miesiąc 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: