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.
366 Commits
3 Branches
9.3 MiB
 
 
 
 
Struktur: 6db62dde15
Branches Tags
${ item.name }
Erstelle Branch ${ searchTerm }
von „6db62dde15“
${ noResults }
res_levis_backend/cmd
Blaz Smehov 6db62dde15 feat: reimplement redis support, using hash maps for quick insert and read vor 1 Woche
..
bridge feat: boilerplate for settings handler, chore: refactor kafka client package name vor 4 Wochen
decoder chore: refactor and move code for beacon logic vor 1 Woche
location feat: reimplement redis support, using hash maps for quick insert and read vor 1 Woche
server feat: reimplement redis support, using hash maps for quick insert and read vor 1 Woche
testbench feat: basis for decoding different beacon types vor 2 Wochen
valkey-testbench feat: reimplement redis support, using hash maps for quick insert and read vor 1 Woche
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: