pollutri
/
res_levis_backend
1
0
Fork 0
Code Issues 1 Pull-Requests 0 Releases 0 Wiki Aktivität
Du kannst nicht mehr als 25 Themen auswählen Themen müssen entweder mit einem Buchstaben oder einer Ziffer beginnen. Sie können Bindestriche („-“) enthalten und bis zu 35 Zeichen lang sein.
415 Commits
3 Branches
9.8 MiB
 
 
 
 
Branch: master
Branches Tags
${ item.name }
Erstelle Branch ${ searchTerm }
von „master“
${ noResults }
res_levis_backend/build
Blaz Smehov f27512f183 feat: add api endpoint for parser registry CRUD operations vor 2 Wochen
..
ci initial directory layout vor 8 Jahren
init-scripts feat: add alerts topic, publish alert messages to MQTT broker from the bridge vor 1 Monat
package feat: add api endpoint for parser registry CRUD operations vor 2 Wochen
README.md build config file location clarification vor 6 Jahren
docker-compose.dev.yml chore: update docker compose, dockerfile of decoder to copy the decoding config, add open api schema for beacon parser vor 3 Wochen
docker-compose.yaml chore: update docker compose, dockerfile of decoder to copy the decoding config, add open api schema for beacon parser vor 3 Wochen

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: