pollutri
/
res_levis_backend
1
0
포크 0
코드 이슈 9 풀 리퀘스트 0 릴리즈 0 위키 활동
25개 이상의 토픽을 선택하실 수 없습니다. Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
455 커밋
3 브랜치
491 MiB
 
 
 
 
트리: d0157ce6ae
브랜치 태그
${ item.name }
${ searchTerm } 브랜치 생성
from 'd0157ce6ae'
${ noResults }
res_levis_backend/build
Blaz Smehov 4892be4ff9 fix: add restart policy to the docker compose 1 주 전
..
ci initial directory layout 8 년 전
env feat: change message retention 1 개월 전
init-scripts fix: add missing kafka topics to init script 2 주 전
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: log cleanup 1 주 전
docker-compose.local.yml fix: add restart policy to the docker compose 1 주 전
docker-compose.yaml chore: log cleanup 1 주 전

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: