pollutri
/
res_levis_backend
1
0
Разклонения 0
Код Задачи 1 Заявки за сливане 0 Версии 0 Уики Activity
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.
394 Ревизии
3 Клонове
9.8 MiB
 
 
 
 
ИН на ревизия: 746130b141
Клонове Маркери
${ item.name }
Create branch ${ searchTerm }
от '746130b141'
${ noResults }
res_levis_backend/cmd
Blaz Smehov 746130b141 feat: verify if tracker is inside the allowed zone преди 1 месец
..
bridge feat: add pulling of configuration from server on start up, updates in db, cleanup in bridge on server startup преди 1 месец
db-testbench chore: valkey cleanup преди 1 месец
decoder chore: update gitignore преди 1 месец
location feat: verify if tracker is inside the allowed zone преди 1 месец
server feat: verify if tracker is inside the allowed zone преди 1 месец
testbench feat: basis for decoding different beacon types преди 2 месеца
token-testbench feat: add pulling of configuration from server on start up, updates in db, cleanup in bridge on server startup преди 1 месец
valkey-testbench feat: implement basic API, reimplement Redis and some methods for quick insert (persistence in case of crash) using hash maps преди 2 месеца
README.md Update cmd/README w/updated example URLs преди 3 години

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: