pollutri
/
res_levis_backend
1
0
Forka 0
Codice Problemi 9 Pull Requests 0 Rilasci 0 Wiki Attività
Non puoi selezionare più di 25 argomenti Gli argomenti devono iniziare con una lettera o un numero, possono includere trattini ('-') e possono essere lunghi fino a 35 caratteri.
421 Commit
3 Rami (Branch)
268 MiB
 
 
 
 
Albero (Tree): d28df4b866
Rami (Branch) Tag
${ item.name }
Crea branch ${ searchTerm }
da '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 settimane fa
..
ci initial directory layout 8 anni fa
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 settimane fa
init-scripts feat: add alerts topic, publish alert messages to MQTT broker from the bridge 2 mesi fa
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 settimane fa
README.md build config file location clarification 7 anni fa
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 settimane fa
docker-compose.woodpecker.yml chore: big refactoring job 4 settimane fa
docker-compose.yaml feat: add script for building the docker containers, change prod docker compose to use built images 3 settimane fa

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: