pollutri
/
res_levis_backend
1
0
Forka 0
Codice Problemi 1 Pull Requests 0 Rilasci 0 Wiki Attività
Non puoi selezionare più di 25 argomenti Gli argomenti devono iniziare con una lettera o un numero, possono includere trattini ('-') e possono essere lunghi fino a 35 caratteri.
415 Commit
3 Rami (Branch)
9.8 MiB
 
 
 
 
Ramo (Branch): master
Rami (Branch) Tag
${ item.name }
Crea branch ${ searchTerm }
da 'master'
${ noResults }
res_levis_backend/build
Blaz Smehov f27512f183 feat: add api endpoint for parser registry CRUD operations 2 settimane fa
..
ci initial directory layout 8 anni fa
init-scripts feat: add alerts topic, publish alert messages to MQTT broker from the bridge 1 mese fa
package feat: add api endpoint for parser registry CRUD operations 2 settimane fa
README.md build config file location clarification 6 anni fa
docker-compose.dev.yml chore: update docker compose, dockerfile of decoder to copy the decoding config, add open api schema for beacon parser 3 settimane fa
docker-compose.yaml chore: update docker compose, dockerfile of decoder to copy the decoding config, add open api schema for beacon parser 3 settimane fa

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: