pollutri
/
res_levis_backend
1
0
Atdalīts 0
Kods Problēmas 9 Izmaiņu pieprasījumi 0 Laidieni 0 Vikivietne Aktivitāte
Nevar pievienot vairāk kā 25 tēmas Tēmai ir jāsākas ar burtu vai ciparu, tā var saturēt domu zīmes ('-') un var būt līdz 35 simboliem gara.
456 Revīzijas
3 Atzari
491 MiB
 
 
 
 
Koks: 3f8c4b60a6
Atzari Tagi
${ item.name }
Izveidot atzaru ${ searchTerm }
no '3f8c4b60a6'
${ noResults }
res_levis_backend/build
Blaz Smehov 4892be4ff9 fix: add restart policy to the docker compose pirms 1 nedēļas
..
ci initial directory layout pirms 8 gadiem
env feat: change message retention pirms 1 mēnesi
init-scripts fix: add missing kafka topics to init script pirms 2 nedēļām
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 pirms 2 mēnešiem
README.md build config file location clarification pirms 7 gadiem
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 pirms 2 mēnešiem
docker-compose.dev.yml chore: log cleanup pirms 1 nedēļas
docker-compose.local.yml fix: add restart policy to the docker compose pirms 1 nedēļas
docker-compose.yaml chore: log cleanup pirms 1 nedēļas

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: