pollutri
/
res_levis_backend
1
0
フォーク 0
コード 課題 1 プルリクエスト 0 リリース 0 Wiki アクティビティ
選択できるのは25トピックまでです。 トピックは、先頭が英数字で、英数字とダッシュ('-')を使用した35文字以内のものにしてください。
401 コミット
3 ブランチ
9.8 MiB
 
 
 
 
ツリー: a2f7dfef08
ブランチ タグ
${ item.name }
ブランチ ${ searchTerm } を作成
'a2f7dfef08' から
${ noResults }
res_levis_backend/build
Blaz Smehov a2f7dfef08 chore: update docker compose, dockerfile of decoder to copy the decoding config, add open api schema for beacon parser 3週間前
..
ci initial directory layout 8年前
init-scripts feat: add alerts topic, publish alert messages to MQTT broker from the bridge 1ヶ月前
package chore: update docker compose, dockerfile of decoder to copy the decoding config, add open api schema for beacon parser 3週間前
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: