pollutri
/
res_levis_backend
1
0
Förgrening 0
Kod Ärenden 9 Pull-förfrågningar 0 Släpp 0 Wiki Aktiviteter
Du kan inte välja fler än 25 ämnen Ämnen måste starta med en bokstav eller siffra, kan innehålla bindestreck ('-') och vara max 35 tecken långa.
456 Incheckningar
3 Grenar
491 MiB
 
 
 
 
Gren: master
Grenar Taggar
${ item.name }
Skapa branchen ${ searchTerm }
från 'master'
${ noResults }
res_levis_backend/build
Blaz Smehov 4892be4ff9 fix: add restart policy to the docker compose 1 vecka sedan
..
ci initial directory layout 8 år sedan
env feat: change message retention 1 månad sedan
init-scripts fix: add missing kafka topics to init script 2 veckor sedan
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 2 månader sedan
README.md build config file location clarification 7 år sedan
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 månader sedan
docker-compose.dev.yml chore: log cleanup 1 vecka sedan
docker-compose.local.yml fix: add restart policy to the docker compose 1 vecka sedan
docker-compose.yaml chore: log cleanup 1 vecka sedan

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: