Repository navigation
Installation
network-tools (the app is called Domain-Monitor) ships as a ready-made Docker image, ghcr.io/roberteinsle/network-tools, and needs a PostgreSQL database. The recommended way to run it is Coolify, but any Docker host works.
- A small Linux server (1–2 CPU cores and 2 GB RAM are plenty for a few hundred domains).
- A domain or subdomain for the backend, with HTTPS (Coolify handles the certificate).
- PostgreSQL (in Coolify: a separate database resource with backups enabled).
- An SMTP mailbox for sending alerts. It is configured later in the backend, not via environment variables.
- Outgoing port 25 if you want the optional STARTTLS check of MX hosts and the DANE certificate comparison. Many cloud providers block it by default.
- Ideally your own recursive resolver (e.g. Unbound) for the blacklist check, because many RBLs refuse queries from public resolvers.
- Every push to
mainbuildsghcr.io/roberteinsle/network-tools:latestvia GitHub Actions. Tagged versions are published as well. - In Coolify, create a PostgreSQL database as its own resource and enable backups there.
- Create a Docker Compose (Empty) resource and paste
deploy/docker-compose.coolify.yml. - Set the variables (see Configuration):
APP_KEY,APP_URL,DB_HOST,DB_PORT,DB_DATABASE,DB_USERNAME,DB_PASSWORD. - On the
appservice, enter your domain with port8080and deploy. - Open the terminal of the
appcontainer in Coolify and create the first user (see First steps).
The compose file starts three services from the same image:
| Service | Purpose |
|---|---|
app |
Web backend on port 8080. Runs the database migrations on start. |
worker |
Runs the domain checks from the queue (queue:work). |
scheduler |
Queues due domains every 5 minutes and prunes old logs at night (schedule:work). |
worker and scheduler only start once app is healthy, so migrations are always finished first.
There are no passwords. Create the first user on the console; the command prints a one-time login link right away, so it works even before SMTP is configured:
php artisan app:user you@example.com --name="Your Name"Then, in the backend:
- Settings → Passkeys: register a passkey for future logins.
- Settings → Email delivery: enter the SMTP server and the sender address, then use Send test mail.
- Settings → Email delivery → Notifications: add the global alert recipients.
- Customers: optionally create customers and pick their DKIM providers.
- Domains: add your domains. The first check runs within five minutes, or immediately via Check now.
Pull a new image tag (or latest) in Coolify and redeploy. Database migrations run automatically when app starts. Take a database backup before every update.
The repository includes a dev container (PHP 8.5, Node 22, Docker-in-Docker) that also works in GitHub Codespaces.
docker compose up -d --build
docker compose exec app php artisan app:user you@example.com
php artisan testWithout SMTP, mails are written to the log (MAIL_MAILER=log).
network-tools · Website · Bugs and ideas: Issues · Generated from handbuch/ – do not edit here
Getting started
Reference
More