pollutri
/
res_levis_backend
1
0
Forkuj 0
Kod Zgłoszenia 9 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.
427 Commity
3 Gałęzie
268 MiB
 
 
 
 
Drzewo: 34cadb4cec
Gałęzie Tagi
${ item.name }
Utwórz gałąź ${ searchTerm }
z '34cadb4cec'
${ noResults }
res_levis_backend/build
Blaz Smehov 5fd72d8151 feat: add new topics, readers and writers 1 tydzień temu
..
ci initial directory layout 8 lat temu
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 tygodni temu
init-scripts feat: add new topics, readers and writers 1 tydzień temu
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 tygodni temu
README.md build config file location clarification 7 lat temu
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 tygodni temu
docker-compose.dev.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 tygodni temu
docker-compose.woodpecker.yml chore: big refactoring job 3 tygodni temu
docker-compose.yaml 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 tygodni 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: