pollutri
/
res_levis_backend
1
0
Bifurcation 0
Code Tickets 9 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.
421 Révisions
3 Branches
268 MiB
 
 
 
 
Aborescence: d28df4b866
Branches Tags
${ item.name }
Créer la branche ${ searchTerm }
de 'd28df4b866'
${ noResults }
res_levis_backend/build
Blaz Smehov d28df4b866 feat: add script for building the docker containers, change prod docker compose to use built images il y a 3 semaines
..
ci initial directory layout il y a 8 ans
env feat: add switching between ml and filter algorithm, various fixes in context use, script for creating docker images, various bug fixes regarding persistence in db, persisting alerts in db and CRUD operations for alerts il y a 3 semaines
init-scripts feat: add alerts topic, publish alert messages to MQTT broker from the bridge il y a 2 mois
package feat: add switching between ml and filter algorithm, various fixes in context use, script for creating docker images, various bug fixes regarding persistence in db, persisting alerts in db and CRUD operations for alerts il y a 3 semaines
README.md build config file location clarification il y a 7 ans
docker-compose.dev.yml feat: add switching between ml and filter algorithm, various fixes in context use, script for creating docker images, various bug fixes regarding persistence in db, persisting alerts in db and CRUD operations for alerts il y a 3 semaines
docker-compose.woodpecker.yml chore: big refactoring job il y a 4 semaines
docker-compose.yaml feat: add script for building the docker containers, change prod docker compose to use built images il y a 3 semaines

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: