pollutri
/
res_levis_backend
1
0
Förgrening 0
Kod Ärenden 9 Pull-förfrågningar 0 Släpp 0 Wiki Aktiviteter
Du kan inte välja fler än 25 ämnen Ämnen måste starta med en bokstav eller siffra, kan innehålla bindestreck ('-') och vara max 35 tecken långa.
421 Incheckningar
3 Grenar
268 MiB
 
 
 
 
Träd: d28df4b866
Grenar Taggar
${ item.name }
Skapa branchen ${ searchTerm }
från '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 3 veckor sedan
..
ci initial directory layout 8 år sedan
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 3 veckor sedan
init-scripts feat: add alerts topic, publish alert messages to MQTT broker from the bridge 2 månader sedan
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 3 veckor sedan
README.md build config file location clarification 7 år sedan
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 3 veckor sedan
docker-compose.woodpecker.yml chore: big refactoring job 4 veckor sedan
docker-compose.yaml feat: add script for building the docker containers, change prod docker compose to use built images 3 veckor sedan

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: