pollutri
/
res_levis_backend
1
0
Forkuj 0
Kod Zgłoszenia 1 Oczekujące zmiany 0 Wydania 0 Wiki Aktywność
Nie możesz wybrać więcej, niż 25 tematów Tematy muszą się zaczynać od litery lub cyfry, mogą zawierać myślniki ('-') i mogą mieć do 35 znaków.
367 Commity
3 Gałęzie
9.3 MiB
 
 
 
 
Drzewo: cfab61e665
Gałęzie Tagi
${ item.name }
Utwórz gałąź ${ searchTerm }
z 'cfab61e665'
${ noResults }
res_levis_backend/cmd
Blaz Smehov 6db62dde15 feat: reimplement redis support, using hash maps for quick insert and read 1 tydzień temu
..
bridge feat: boilerplate for settings handler, chore: refactor kafka client package name 4 tygodni temu
decoder chore: refactor and move code for beacon logic 1 tydzień temu
location feat: reimplement redis support, using hash maps for quick insert and read 1 tydzień temu
server feat: reimplement redis support, using hash maps for quick insert and read 1 tydzień temu
testbench feat: basis for decoding different beacon types 2 tygodni temu
valkey-testbench feat: reimplement redis support, using hash maps for quick insert and read 1 tydzień temu
README.md Update cmd/README w/updated example URLs 3 lat temu

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: