pollutri
/
res_levis_backend
1
0
Fork 0
Código Incidencias 1 Pull Requests 0 Lanzamientos 0 Wiki Actividad
No puede seleccionar más de 25 temas Los temas deben comenzar con una letra o número, pueden incluir guiones ('-') y pueden tener hasta 35 caracteres de largo.
401 Commits
3 Ramas
9.8 MiB
 
 
 
 
Árbol: a2f7dfef08
Ramas Etiquetas
${ item.name }
Crear rama ${ searchTerm }
desde 'a2f7dfef08'
${ noResults }
res_levis_backend/build
Blaz Smehov a2f7dfef08 chore: update docker compose, dockerfile of decoder to copy the decoding config, add open api schema for beacon parser hace 3 semanas
..
ci initial directory layout hace 8 años
init-scripts feat: add alerts topic, publish alert messages to MQTT broker from the bridge hace 1 mes
package chore: update docker compose, dockerfile of decoder to copy the decoding config, add open api schema for beacon parser hace 3 semanas
README.md build config file location clarification hace 6 años
docker-compose.dev.yml chore: update docker compose, dockerfile of decoder to copy the decoding config, add open api schema for beacon parser hace 3 semanas
docker-compose.yaml chore: update docker compose, dockerfile of decoder to copy the decoding config, add open api schema for beacon parser hace 3 semanas

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: