pollutri
/
res_levis_backend
1
0
Форкнуть 0
Код Задачи 1 Pull Request'ы 0 Релизы 0 Вики Активность
Вы не можете выбрать более 25 тем Темы должны начинаться с буквы или цифры, могут содержать дефисы(-) и должны содержать не более 35 символов.
409 коммитов
3 Ветки
9.8 MiB
 
 
 
 
Дерево: 84124cff13
Ветки Теги
${ item.name }
Создать ветку ${ searchTerm }
из '84124cff13'
${ noResults }
res_levis_backend/build
Blaz Smehov f27512f183 feat: add api endpoint for parser registry CRUD operations 2 недель назад
..
ci initial directory layout 8 лет назад
init-scripts feat: add alerts topic, publish alert messages to MQTT broker from the bridge 1 месяц назад
package feat: add api endpoint for parser registry CRUD operations 2 недель назад
README.md build config file location clarification 6 лет назад
docker-compose.dev.yml chore: update docker compose, dockerfile of decoder to copy the decoding config, add open api schema for beacon parser 3 недель назад
docker-compose.yaml chore: update docker compose, dockerfile of decoder to copy the decoding config, add open api schema for beacon parser 3 недель назад

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: