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.
375 Commit
3 Rami (Branch)
9.3 MiB
 
 
 
 
Albero (Tree): d69952a36d
Rami (Branch) Tag
${ item.name }
Crea branch ${ searchTerm }
da 'd69952a36d'
${ noResults }
res_levis_backend/build
Blaz Smehov d69952a36d chore: add settings topic to init script 3 giorni fa
..
ci initial directory layout 8 anni fa
init-scripts chore: add settings topic to init script 3 giorni fa
package feat: add websocket and dockerfile to build location 3 giorni 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: