pollutri
/
res_levis_backend
1
0
Derivar 0
Código Questões 1 Pedidos de integração 0 Lançamentos 0 Wiki Trabalho
Não pode escolher mais do que 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.
415 Cometimentos
3 Ramos
9.8 MiB
 
 
 
 
Ramo: master
Ramos Etiquetas
${ item.name }
Criar ramo ${ searchTerm }
de 'master'
${ noResults }
res_levis_backend/build
Blaz Smehov f27512f183 feat: add api endpoint for parser registry CRUD operations há 2 semanas
..
ci initial directory layout há 8 anos
init-scripts feat: add alerts topic, publish alert messages to MQTT broker from the bridge há 1 mês
package feat: add api endpoint for parser registry CRUD operations há 2 semanas
README.md build config file location clarification há 6 anos
docker-compose.dev.yml chore: update docker compose, dockerfile of decoder to copy the decoding config, add open api schema for beacon parser há 3 semanas
docker-compose.yaml chore: update docker compose, dockerfile of decoder to copy the decoding config, add open api schema for beacon parser há 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: