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.
397 Commits
3 Ramas
9.8 MiB
 
 
 
 
Árbol: d1bd509eef
Ramas Etiquetas
${ item.name }
Crear rama ${ searchTerm }
desde 'd1bd509eef'
${ noResults }
res_levis_backend/build
Blaz Smehov 1afa01b5c5 feat: add alerts topic, publish alert messages to MQTT broker from the bridge hace 1 mes
..
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: remove unused files, add dev docker compose and dockerfile for live rebuilds and testing hace 1 mes
README.md build config file location clarification hace 6 años
docker-compose.prod.yaml chore: remove unused files, add dev docker compose and dockerfile for live rebuilds and testing hace 1 mes
docker-compose.yml chore: remove unused files, add dev docker compose and dockerfile for live rebuilds and testing hace 1 mes

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: