pollutri
/
res_levis_backend
1
0
Fork 0
Code Issues 9 Pull-Requests 0 Releases 0 Wiki Aktivität
Du kannst nicht mehr als 25 Themen auswählen Themen müssen entweder mit einem Buchstaben oder einer Ziffer beginnen. Sie können Bindestriche („-“) enthalten und bis zu 35 Zeichen lang sein.
449 Commits
3 Branches
491 MiB
 
 
 
 
Struktur: c917ace01e
Branches Tags
${ item.name }
Erstelle Branch ${ searchTerm }
von „c917ace01e“
${ noResults }
res_levis_backend/build
Blaz Smehov 4892be4ff9 fix: add restart policy to the docker compose vor 1 Woche
..
ci initial directory layout vor 8 Jahren
env feat: change message retention vor 1 Monat
init-scripts fix: add missing kafka topics to init script vor 2 Wochen
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 vor 2 Monaten
README.md build config file location clarification vor 7 Jahren
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 vor 2 Monaten
docker-compose.dev.yml chore: log cleanup vor 1 Woche
docker-compose.local.yml fix: add restart policy to the docker compose vor 1 Woche
docker-compose.yaml chore: log cleanup vor 1 Woche

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: