pollutri
/
res_levis_backend
1
0
Bifurcation 0
Code Tickets 1 Demandes d'ajout 0 Versions 0 Wiki Activité
Vous ne pouvez pas sélectionner plus de 25 sujets Les noms de sujets doivent commencer par une lettre ou un nombre, peuvent contenir des tirets ('-') et peuvent comporter jusqu'à 35 caractères.
361 Révisions
3 Branches
9.3 MiB
 
 
 
 
Aborescence: 5cc3b5f1d2
Branches Tags
${ item.name }
Créer la branche ${ searchTerm }
de '5cc3b5f1d2'
${ noResults }
res_levis_backend/build
Blaz Smehov 4b872a5cc0 feat: locations algorithm, chore: remove unused files il y a 1 semaine
..
ci initial directory layout il y a 8 ans
init-scripts feat: locations algorithm, chore: remove unused files il y a 1 semaine
package chore: add health check for EMQX, bridge service awaits check il y a 1 mois
README.md build config file location clarification il y a 6 ans
docker-compose.yaml chore: update docker compose with kafdrop and automatic topic creation il y a 1 semaine

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: