pollutri
/
res_levis_backend
1
0
Fork 0
Koodi Ongelmat 1 Pull-pyynnöt 0 Julkaisut 0 Wiki Toiminta
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
371 Commitit
3 Branchit
9.3 MiB
 
 
 
 
Puu: e14d8e0d97
Branchit Tagit
${ item.name }
Create branch ${ searchTerm }
from 'e14d8e0d97'
${ noResults }
res_levis_backend/cmd
Blaz Smehov e14d8e0d97 graceful shutdown of redis client 5 päivää sitten
..
bridge feat: gracefully close kafka connections on docker sigterm signal 5 päivää sitten
decoder feat: gracefully close kafka connections on docker sigterm signal 5 päivää sitten
location feat: gracefully close kafka connections on docker sigterm signal 5 päivää sitten
server graceful shutdown of redis client 5 päivää sitten
testbench feat: basis for decoding different beacon types 2 viikkoa sitten
valkey-testbench feat: implement basic API, reimplement Redis and some methods for quick insert (persistence in case of crash) using hash maps 1 viikko sitten
README.md Update cmd/README w/updated example URLs 3 vuotta sitten

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: