pollutri
/
res_levis_backend
1
0
Forka 0
Codice Problemi 1 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.
373 Commit
3 Rami (Branch)
9.3 MiB
 
 
 
 
Albero (Tree): 979563eec4
Rami (Branch) Tag
${ item.name }
Crea branch ${ searchTerm }
da '979563eec4'
${ noResults }
res_levis_backend/build
Blaz Smehov 6db62dde15 feat: reimplement redis support, using hash maps for quick insert and read 1 settimana fa
..
ci initial directory layout 8 anni fa
init-scripts feat: locations algorithm, chore: remove unused files 1 settimana fa
package chore: add health check for EMQX, bridge service awaits check 1 mese fa
README.md build config file location clarification 6 anni fa
docker-compose.yaml feat: reimplement redis support, using hash maps for quick insert and read 1 settimana 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: