pollutri
/
res_levis_backend
1
0
포크 0
코드 이슈 1 풀 리퀘스트 0 릴리즈 0 위키 활동
25개 이상의 토픽을 선택하실 수 없습니다. Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
413 커밋
3 브랜치
9.8 MiB
 
 
 
 
트리: 23208dc32d
브랜치 태그
${ item.name }
${ searchTerm } 브랜치 생성
from '23208dc32d'
${ noResults }
res_levis_backend/build
Blaz Smehov f27512f183 feat: add api endpoint for parser registry CRUD operations 2 주 전
..
ci initial directory layout 8 년 전
init-scripts feat: add alerts topic, publish alert messages to MQTT broker from the bridge 1 개월 전
package feat: add api endpoint for parser registry CRUD operations 2 주 전
README.md build config file location clarification 6 년 전
docker-compose.dev.yml chore: update docker compose, dockerfile of decoder to copy the decoding config, add open api schema for beacon parser 3 주 전
docker-compose.yaml chore: update docker compose, dockerfile of decoder to copy the decoding config, add open api schema for beacon parser 3 주 전

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: