pollutri
/
res_levis_backend
1
0
Креирај огранак 0
Код Дискусије 9 Захтеви за спајање 0 Издања 0 Вики Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
437 Комити
3 Гране
491 MiB
 
 
 
 
Дрво: dd07081da2
Гране Ознаке
${ item.name }
Create branch ${ searchTerm }
from 'dd07081da2'
${ noResults }
res_levis_backend/build
Blaz Smehov 04574f16d8 feat: change message retention пре 1 месец
..
ci initial directory layout пре 8 година
env feat: change message retention пре 1 месец
init-scripts feat: change message retention пре 1 месец
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 месеци
README.md build config file location clarification пре 7 година
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 месеци
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 месеци
docker-compose.woodpecker.yml chore: big refactoring job пре 2 месеци
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 месеци

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: