e4754b342b
al correr `make ota build save` se genera un entorno de staging en panel.staging.sutty.nl con los datos de los sitios y una copia de la base de datos. no copiamos los sitios porque les usuaries van a entrar a hacer pruebas en staging y esperar encontrar los cambios luego en producción. además usaría mucho almacenamiento hacer copias. al correr `make env=production ota build save` se realiza el mismo proceso para producción. los assets se alojan por fuera para que podamos actualizarlos sin tocar el contenedor y separar los de production de los de staging. estos cambios van en línea con ansible-sutty-deploy.
32 lines
1 KiB
Plaintext
32 lines
1 KiB
Plaintext
check process sutty with pidfile /srv/http/tmp/puma.pid
|
|
start program = "/usr/local/bin/sutty sutty"
|
|
stop program = "/bin/sh -c 'cat /srv/http/tmp/puma.pid | xargs kill'"
|
|
|
|
check process prometheus with pidfile /tmp/prometheus.pid
|
|
start program = "/usr/local/bin/sutty prometheus"
|
|
stop program = "/bin/sh -c 'cat /tmp/prometheus.pid | xargs kill'"
|
|
|
|
check program blazer_5m
|
|
with path "/bin/sh -c 'cd /srv/http && foreman start blazer_5m'"
|
|
as uid "app" and gid "www-data"
|
|
every 5 cycles
|
|
if status != 0 then alert
|
|
|
|
check program blazer_1h
|
|
with path "/bin/sh -c 'cd /srv/http && foreman start blazer_1h'"
|
|
as uid "app" and gid "www-data"
|
|
every 60 cycles
|
|
if status != 0 then alert
|
|
|
|
check program blazer_1d
|
|
with path "/bin/sh -c 'cd /srv/http && foreman start blazer_1d'"
|
|
as uid "app" and gid "www-data"
|
|
every 1440 cycles
|
|
if status != 0 then alert
|
|
|
|
check program blazer
|
|
with path "/bin/sh -c 'cd /srv/http && foreman start blazer'"
|
|
as uid "app" and gid "www-data"
|
|
every 61 cycles
|
|
if status != 0 then alert
|