vjrj
72975e44ae
groucho (5,9 GB, compartidos con Mongo 7 + web + notifications + redis + node-red) se quedo sin ssh compilando un `meteor build` y hubo que reiniciarlo. El host de despliegue no debe compilar: debe recibir una imagen. Workflow para el runner de Forgejo en aaron. Dos decisiones que conviene no deshacer sin leer fase-9-ci-imagenes.md: - Kaniko en vez de `docker build`: aaron es host COMPARTIDO (git.comunes.org, Jenkins, GlitchTip). `docker build` obligaria a montar /var/run/docker.sock en el job (root equivalente sobre aaron) y ademas el limite de memoria del job no serviria de nada, porque quien construye es el demonio, fuera del contenedor. Kaniko construye DENTRO del job: sin socket y con `--memory` que si acota al que come la RAM. - `--memory=4g --memory-swap=4g`: swap a cero adrede. Preferimos que muera el build a que aaron pagine y se lleve la forja por delante. De momento solo `workflow_dispatch`. El disparo por push queda comentado hasta que git.comunes.org salga de detras de Cloudflare (la capa del bundle son 508 MB contra un tope de 100 MB del plan gratuito: el push se queda en Retrying eterno) y existan los secretos REGISTRY_USER/REGISTRY_TOKEN. |
||
|---|---|---|
| .forgejo/workflows | ||
| .meteor | ||
| bin | ||
| client | ||
| cucumber | ||
| designs | ||
| docker | ||
| imports | ||
| packages | ||
| private | ||
| public | ||
| scripts | ||
| secrets | ||
| server | ||
| smoke | ||
| test/server | ||
| .dockerignore | ||
| .gitignore | ||
| .meteorignore | ||
| .npmrc | ||
| API.md | ||
| COPYRIGHT.md | ||
| docker-compose.staging.yml | ||
| docker-compose.yml | ||
| Dockerfile | ||
| fonts.json | ||
| History.md | ||
| LICENSE.md | ||
| package-lock.json | ||
| package.json | ||
| PENDIENTE.md | ||
| README.md | ||
| RUNBOOK.md | ||
| settings-development-sample.json | ||
| UPGRADE.md | ||
Tod@s contra el Fuego (All Against Fire)
This is web service that notifies about fires detected in an area of your interest. It helps the early detection of fires and facilitates local mobilization, while the professional extinction services arrive.
Install
Prerrequisites: a running meteor (we share the fuegos database with the telegram bot).
Install meteor and run meteor npm install and npm start
Some other development deps (in debian & ubuntu):
apt-get install libcairo2-dev libjpeg-dev libgif-dev pkg-config
GeoIP
Configure mirror and cron of the geoip database.
Telegram bot
See our bot.
More platforms and services in the future...
Tests
We do tests via:
TEST_PORT=3000 TEST_WATCH=1 TEST_CLIENT=0 MONGO_URL=mongodb://localhost:27017/fuegostest meteor --settings settings-development.json test --driver-package meteortesting:mocha --port 3010
# and
node_modules/.bin/chimp --watch --ddp=http://localhost:3000 --path=cucumber
# and
node_modules/.bin/chimp --ddp=http://localhost:3000 --path=cucumber
FAQ & Troubleshooting
Q - I get something like (...) /node_modules/fibers/future.js:280 (...) Error: Could not locate the bindings file. What can I do?
A - Try meteor npm rebuild
Data source acknowledgements
We acknowledge the use of data and imagery from LANCE FIRMS operated by the NASA/GSFC/Earth Science Data and Information System (ESDIS) with funding provided by NASA/HQ.
License
GNU APLv3. See our LICENSE, for a complete text.
Thanks & other acknowlegments
Thanks indeed to:
- Lupe Bao Reixa for Galician translation