twothatit 27c91eee95 Fix deploy crash: use valid log status 'info' instead of 'warning' ...

The deployment_logs table has a CHECK constraint allowing only
'success', 'error', 'info'. Using 'warning' caused an IntegrityError
that crashed the entire deployment.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

2026-02-08 22:23:52 +01:00

..

routers

Add i18n, branding, user management, health checks, and cleanup for deployment

2026-02-08 17:24:05 +01:00

services

Fix deploy crash: use valid log status 'info' instead of 'warning'

2026-02-08 22:23:52 +01:00

utils

Add i18n, branding, user management, health checks, and cleanup for deployment

2026-02-08 17:24:05 +01:00

__init__.py

First Build alpha 0.1

2026-02-07 12:18:20 +01:00

database.py

Fix NPM integration: correct forward host, SSL, and add UDP stream

2026-02-08 19:51:32 +01:00

dependencies.py

First Build alpha 0.1

2026-02-07 12:18:20 +01:00

main.py

Add i18n, branding, user management, health checks, and cleanup for deployment

2026-02-08 17:24:05 +01:00

models.py

Fix NPM integration: correct forward host, SSL, and add UDP stream

2026-02-08 19:51:32 +01:00