Coordinator setup (one command)#

koordinator-kur.sh turns a Linux server into a working reference coordinator in a few minutes. The coordinator only validates and averages adapters; no GPU is needed, a small server is enough.

What you need first#

• A Linux server (Ubuntu, Debian, Arch and other glibc-based distributions; x86_64 or aarch64) with root (sudo) access, at least ~2 GB of memory and ~3 GB of free disk (more as your data grows).
• A domain name with an A record pointing to the server (for HTTPS) and ports 80 and 443 open.
• Your training data: plain text files (.txt, .md, .jsonl). The source and licence of the data are your responsibility; Modelen neither provides nor selects data. See Integration options.

Install#

curl -fsSL https://github.com/macbyclp/modelen-tr/releases/latest/download/koordinator-kur.sh -o koordinator-kur.sh
bash koordinator-kur.sh --dene                      # see what it would do first (installs nothing)
sudo bash koordinator-kur.sh --alan-adi coordinator.example.org --veri ./texts/

When it finishes, the coordinator is running, the protocol conformance test has run by itself, and your shared key and the next steps are printed.

What gets installed?#

After install: connecting to the portal#

1. DNS. Point your domain's A record at the server and open 80 and 443 (Caddy then gets the certificate).
2. Application. Create an account on modelen.tr, verify your e-mail, and apply via Panel → Application; use https://your-domain as the address. See Becoming a coordinator.
3. Address verification. The portal gives you a value; publish it with this command, then have the portal check it: ``bash sudo modelen-koordinator dogrulama modelen-dogrulama-AbC123... `` Details: Address verification.
4. Heartbeat. Create a key under Panel → API keys and start the heartbeat service; your coordinator then shows as "online" in the directory: ``bash sudo modelen-koordinator nabiz mdl_... `` It works even when your coordinator is key-protected (closed). See Heartbeat.
5. Volunteers. In a closed group you hand the key to volunteers (modelen-koordinator anahtar). To open it to everyone: modelen-koordinator acik.

Management commands#

Security notes#

• The key is not visible in the process list (ps): it lives in an environment file (koordinator.env, readable only by root and the service user).
• The coordinator listens only on 127.0.0.1; only the HTTPS proxy faces the outside. A per-IP rate limit and a worker-count limit are on (Reference coordinator).
• Open mode (no key) lets anyone submit results. Poisoning protection is only simple outlier elimination and structural validation; it is not enough against a determined attacker (Security). We recommend starting with a closed group.
• The content and licence of your training data are your responsibility.

Updating and removing#

• Update: run the script again with the same options. The existing key, round state and work folder are kept.
• Remove: sudo modelen-koordinator kaldir, then, if you like, sudo rm -rf /opt/modelen-koordinator.

If the server already runs a web server#

If 80/443 are in use, Caddy is not installed. At the end the script prints a ready snippet. For an existing Caddy:

coordinator.example.org {
    handle /.well-known/modelen-dogrulama.txt {
        root * /opt/modelen-koordinator/dogrulama
        rewrite * /dogrulama.txt
        file_server
    }
    reverse_proxy 127.0.0.1:8750
}

For nginx: location / { proxy_pass http://127.0.0.1:8750; } plus location = /.well-known/modelen-dogrulama.txt { alias /opt/modelen-koordinator/dogrulama/dogrulama.txt; }. If you gave the script --alan-adi, the coordinator starts with --vekil, so the IP limit sees the real client address the proxy forwards (X-Forwarded-For).

Troubleshooting#

By hand (without the script)#

If you prefer not to use the script you can set everything up yourself: see Reference coordinator and Write your own coordinator.