pollutri
/
res_levis_backend
1
0
Fork 0
Code Issues 9 Pull Requests 0 Releases 0 Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
425 Commits
3 Branches
268 MiB
 
 
 
 
Tree: 5fd72d8151
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from '5fd72d8151'
${ noResults }
res_levis_backend/build
Blaz Smehov 5fd72d8151 feat: add new topics, readers and writers 1 week ago
..
ci initial directory layout 8 years ago
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 weeks ago
init-scripts feat: add new topics, readers and writers 1 week ago
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 weeks ago
README.md build config file location clarification 7 years ago
docker-compose.db.yml chore: several fixes, including token, kafka backoff, timeouts, using context with timeout, adding volumes to postgres and kafka, scripts for creating and restoring sql dump 2 weeks ago
docker-compose.dev.yml chore: several fixes, including token, kafka backoff, timeouts, using context with timeout, adding volumes to postgres and kafka, scripts for creating and restoring sql dump 2 weeks ago
docker-compose.woodpecker.yml chore: big refactoring job 3 weeks ago
docker-compose.yaml chore: several fixes, including token, kafka backoff, timeouts, using context with timeout, adding volumes to postgres and kafka, scripts for creating and restoring sql dump 2 weeks ago

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: