Nerve signal path

Coolify deploy alerts to your phone

Send Coolify deployment results as encrypted Nerve signals. Keep deploy notifications private and separate from chat noise.

How to use it

Use this for deploy failed, build failed, restart loop, migration failed, or container health events.

Copy sender DSN from NerveOps, save it as an environment secret, then pipe a short operational event into nerve send.

export NERVE_DSN="nerve://..."
coolify deploy || echo "coolify deploy failed" | nerve send

Why Nerve here

Nerve is not a full monitoring suite. Keep your existing monitor, deploy tool, or alert source; use Nerve as the encrypted phone signal path.

Sender DSNSender DSN is send-only. It can create signals in one pipe, but it cannot read history, decrypt content, connect as an agent, or execute commands.
RelayThe relay routes ciphertext. The phone receives the push and decrypts locally.
AgentUse nerve-agent only when you explicitly want signed actions on a trusted machine.

Security boundary

Nerve keeps the operational path narrow: sender DSN creates encrypted signals, the relay routes ciphertext, and the phone decrypts locally. If you later need actions, nerve-agent is a separate opt-in step.

FAQ

Does this replace my monitoring system?

No. Nerve receives signals from your existing tool and delivers them as encrypted mobile alerts.

Can the sender DSN read old alerts?

No. Sender credentials are scoped to send-only delivery.