Vous ne pouvez pas sélectionner plus de 25 sujets Les noms de sujets doivent commencer par une lettre ou un nombre, peuvent contenir des tirets ('-') et peuvent comporter jusqu'à 35 caractères.
 
 
 
 
Blaz Smehov d51dc38beb feat: add sending of tracker information over the MQTT broker il y a 2 semaines
..
bridge feat: add sending of tracker information over the MQTT broker il y a 2 semaines
db-testbench chore: valkey cleanup il y a 1 mois
decoder feat: add api endpoint for parser registry CRUD operations il y a 2 semaines
decoder-parser-testbench feat: dynamic decoder testbench il y a 4 semaines
location feat: add sending of tracker information over the MQTT broker il y a 2 semaines
server feat: add sending of tracker information over the MQTT broker il y a 2 semaines
testbench feat: basis for decoding different beacon types il y a 2 mois
token-testbench feat: add pulling of configuration from server on start up, updates in db, cleanup in bridge on server startup il y a 1 mois
valkey-testbench feat: implement basic API, reimplement Redis and some methods for quick insert (persistence in case of crash) using hash maps il y a 2 mois
README.md Update cmd/README w/updated example URLs il y a 3 ans

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: