pollutri
/
res_levis_backend
1
0
Vork 0
Code Kwesties 1 Pull-aanvragen 0 Publicaties 0 Wiki Activiteit
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.
407 Commits
3 Branches
9.8 MiB
 
 
 
 
Tree: ba52f7f411
Branches Labels
${ item.name }
Maak branch ${ searchTerm }
van 'ba52f7f411'
${ noResults }
res_levis_backend/cmd
Blaz Smehov ba52f7f411 chore: refactor logger, add tests 2 weken geleden
..
bridge chore: refactor logger, add tests 2 weken geleden
db-testbench chore: valkey cleanup 1 maand geleden
decoder chore: refactor logger, add tests 2 weken geleden
decoder-parser-testbench feat: dynamic decoder testbench 4 weken geleden
location chore: refactor logger, add tests 2 weken geleden
server chore: refactor logger, add tests 2 weken geleden
testbench feat: basis for decoding different beacon types 2 maanden geleden
token-testbench feat: add pulling of configuration from server on start up, updates in db, cleanup in bridge on server startup 1 maand geleden
valkey-testbench feat: implement basic API, reimplement Redis and some methods for quick insert (persistence in case of crash) using hash maps 2 maanden geleden
README.md Update cmd/README w/updated example URLs 3 jaren geleden

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: