pollutri
/
res_levis_backend
1
0
フォーク 0
コード 課題 1 プルリクエスト 0 リリース 0 Wiki アクティビティ
選択できるのは25トピックまでです。 トピックは、先頭が英数字で、英数字とダッシュ('-')を使用した35文字以内のものにしてください。
406 コミット
3 ブランチ
9.8 MiB
 
 
 
 
ツリー: d51dc38beb
ブランチ タグ
${ item.name }
ブランチ ${ searchTerm } を作成
'd51dc38beb' から
${ noResults }
res_levis_backend/cmd
Blaz Smehov d51dc38beb feat: add sending of tracker information over the MQTT broker 2週間前
..
bridge feat: add sending of tracker information over the MQTT broker 2週間前
db-testbench chore: valkey cleanup 1ヶ月前
decoder feat: add api endpoint for parser registry CRUD operations 2週間前
decoder-parser-testbench feat: dynamic decoder testbench 4週間前
location feat: add sending of tracker information over the MQTT broker 2週間前
server feat: add sending of tracker information over the MQTT broker 2週間前
testbench feat: basis for decoding different beacon types 2ヶ月前
token-testbench feat: add pulling of configuration from server on start up, updates in db, cleanup in bridge on server startup 1ヶ月前
valkey-testbench feat: implement basic API, reimplement Redis and some methods for quick insert (persistence in case of crash) using hash maps 2ヶ月前
README.md Update cmd/README w/updated example URLs 3年前

README.md

/cmd

Main applications for this project.

The directory name for each application should match the name of the executable you want to have (e.g., /cmd/myapp).

Don’t put a lot of code in the application directory. If you think the code can be imported and used in other projects, then it should live in the /pkg directory. If the code is not reusable or if you don’t want others to reuse it, put that code in the /internal directory. You’ll be surprised what others will do, so be explicit about your intentions!

It’s common to have a small main function that imports and invokes the code from the /internal and /pkg directories and nothing else.

Examples: