pollutri
/
res_levis_backend
1
0
Bifurcation 0
Code Tickets 1 Demandes d'ajout 0 Versions 0 Wiki Activité
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.
371 Révisions
3 Branches
9.3 MiB
 
 
 
 
Aborescence: e14d8e0d97
Branches Tags
${ item.name }
Créer la branche ${ searchTerm }
de 'e14d8e0d97'
${ noResults }
res_levis_backend/cmd
Blaz Smehov e14d8e0d97 graceful shutdown of redis client il y a 5 jours
..
bridge feat: gracefully close kafka connections on docker sigterm signal il y a 5 jours
decoder feat: gracefully close kafka connections on docker sigterm signal il y a 5 jours
location feat: gracefully close kafka connections on docker sigterm signal il y a 5 jours
server graceful shutdown of redis client il y a 5 jours
testbench feat: basis for decoding different beacon types il y a 2 semaines
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 1 semaine
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: