pollutri
/
res_levis_backend
1
0
Atdalīts 0
Kods Problēmas 1 Izmaiņu pieprasījumi 0 Laidieni 0 Vikivietne Aktivitāte
Nevar pievienot vairāk kā 25 tēmas Tēmai ir jāsākas ar burtu vai ciparu, tā var saturēt domu zīmes ('-') un var būt līdz 35 simboliem gara.
404 Revīzijas
3 Atzari
9.8 MiB
 
 
 
 
Koks: f27512f183
Atzari Tagi
${ item.name }
Izveidot atzaru ${ searchTerm }
no 'f27512f183'
${ noResults }
res_levis_backend/build
Blaz Smehov f27512f183 feat: add api endpoint for parser registry CRUD operations pirms 2 nedēļām
..
ci initial directory layout pirms 8 gadiem
init-scripts feat: add alerts topic, publish alert messages to MQTT broker from the bridge pirms 1 mēnesi
package feat: add api endpoint for parser registry CRUD operations pirms 2 nedēļām
README.md build config file location clarification pirms 6 gadiem
docker-compose.dev.yml chore: update docker compose, dockerfile of decoder to copy the decoding config, add open api schema for beacon parser pirms 3 nedēļām
docker-compose.yaml chore: update docker compose, dockerfile of decoder to copy the decoding config, add open api schema for beacon parser pirms 3 nedēļām

README.md

/build

Packaging and Continuous Integration.

Put your cloud (AMI), container (Docker), OS (deb, rpm, pkg) package configurations and scripts in the /build/package directory.

Put your CI (travis, circle, drone) configurations and scripts in the /build/ci directory. Note that some of the CI tools (e.g., Travis CI) are very picky about the location of their config files. Try putting the config files in the /build/ci directory linking them to the location where the CI tools expect them when possible (don’t worry if it’s not and if keeping those files in the root directory makes your life easier :-)).

Examples: