pollutri
/
res_levis_backend
1
0
Fork 0
Código Issues 1 Pull requests 0 Versões 0 Wiki Atividade
Você não pode selecionar mais de 25 tópicos Os tópicos devem começar com uma letra ou um número, podem incluir traços ('-') e podem ter até 35 caracteres.
401 Commits
3 Branches
9.8 MiB
 
 
 
 
Tag: a2f7dfef08
Branches Tags
${ item.name }
Criar branch ${ searchTerm }
de 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 3 semanas atrás
..
ci initial directory layout 8 anos atrás
init-scripts feat: add alerts topic, publish alert messages to MQTT broker from the bridge 1 mês atrás
package chore: update docker compose, dockerfile of decoder to copy the decoding config, add open api schema for beacon parser 3 semanas atrás
README.md build config file location clarification 6 anos atrás
docker-compose.dev.yml chore: update docker compose, dockerfile of decoder to copy the decoding config, add open api schema for beacon parser 3 semanas atrás
docker-compose.yaml chore: update docker compose, dockerfile of decoder to copy the decoding config, add open api schema for beacon parser 3 semanas atrás

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: