pollutri
/
res_levis_backend
1
0
Fork 0
Code Issues 1 Pull-Requests 0 Releases 0 Wiki Aktivität
Du kannst nicht mehr als 25 Themen auswählen Themen müssen entweder mit einem Buchstaben oder einer Ziffer beginnen. Sie können Bindestriche („-“) enthalten und bis zu 35 Zeichen lang sein.
395 Commits
3 Branches
9.8 MiB
 
 
 
 
Struktur: 1afa01b5c5
Branches Tags
${ item.name }
Erstelle Branch ${ searchTerm }
von „1afa01b5c5“
${ noResults }
res_levis_backend/cmd
Blaz Smehov 1afa01b5c5 feat: add alerts topic, publish alert messages to MQTT broker from the bridge vor 1 Monat
..
bridge feat: add alerts topic, publish alert messages to MQTT broker from the bridge vor 1 Monat
db-testbench chore: valkey cleanup vor 1 Monat
decoder chore: update gitignore vor 1 Monat
location feat: verify if tracker is inside the allowed zone vor 1 Monat
server feat: add alerts topic, publish alert messages to MQTT broker from the bridge vor 1 Monat
testbench feat: basis for decoding different beacon types vor 2 Monaten
token-testbench feat: add pulling of configuration from server on start up, updates in db, cleanup in bridge on server startup vor 1 Monat
valkey-testbench feat: implement basic API, reimplement Redis and some methods for quick insert (persistence in case of crash) using hash maps vor 2 Monaten
README.md Update cmd/README w/updated example URLs vor 3 Jahren

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: