Requirements: JDK 21+

./gradlew shadowJar   # fat-jar with all dependencies (recommended)
./gradlew build       # all jars
./gradlew test        # run the test suite

• Ktor — asynchronous web framework (Netty engine)
• Clikt — command-line parsing
• Mordant — terminal styling
• Hoplite — HOCON configuration
• kotlinx.serialization — JSON
• Commons Compress + XZ — read .apg (tar.xz) natively
• Logback — logging

• APG-native. Reads package metadata from inside each .apg (tar.xz) exactly as libAPG does, so the index always matches what clients install.
• Repository index. Generates a canonical repodata.json over a pool/ directory laid out as pool/<channel>/<name>/<arch>/<name>-<version>-<arch>.apg.
• Clean REST v2 API for browsing, searching, and downloading packages.
• Signature-safe. Package bytes are stored and served verbatim — never repackaged — so detached .apg.sig signatures stay valid.
• Authenticated publishing. Bearer-token-gated upload (multipart) with apgcheck-style validation, plus delete (yank).
• Protection. Per-IP request rate limiting with automatic bans, and per-IP concurrent-download caps + optional throughput throttling.
• Operations. Interactive admin console (ban/unban/log/metrics/reindex/…), periodic metrics, a bounded request log, and TLS/HTTPS.
• Tolerant reader. Accepts the ecosystem's known inconsistencies (metadata.json/meta.json, either checksum line order, hyphenated or non-hyphenated script names) and emits canonical output.

# Start the server (interactive admin console attached)
java -jar tulpar-server-2.0.0-all.jar start

# Custom config / port / detached
java -jar tulpar-server-2.0.0-all.jar start --config /path/to/application.conf
java -jar tulpar-server-2.0.0-all.jar start --port 8080 --daemon

# Validate a package against the APG spec
java -jar tulpar-server-2.0.0-all.jar check ./mypkg-1.0.0-x86_64.apg

# Version / help
java -jar tulpar-server-2.0.0-all.jar version
java -jar tulpar-server-2.0.0-all.jar --help

When started in the foreground, an interactive console is available:

help, packages, reindex, metrics, log [n], ban <ip>, unban <ip>, banlist, version, restart, stop.

curl -X POST http://localhost:8080/api/v2/packages \
  -H "Authorization: Bearer <token>" \
  -F "apg=@mypkg-1.0.0-x86_64.apg" \
  -F "sig=@mypkg-1.0.0-x86_64.apg.sig" \
  -F "channel=main"

An .apg is a tar.xz archive containing:

metadata.json   package metadata (name, version, type, architecture, …)
data/           files extracted to the system root
md5sums         checksums (v1)
crc32sums       checksums (v2 adds this)
scripts/        optional pre/post install/remove scripts
home/           optional files extracted to $HOME

See apg-docs for the full spec.

Tulpar Server uses HOCON. Create application.conf in the working directory (any omitted value falls back to the built-in default):

server {
    address = "0.0.0.0"
    port = 8080            # ports below 1024 need root
    runInBackground = false
    httpsRedirect = false
    behindProxy = false    # trust X-Forwarded-For only behind a known proxy
    tls {
        enabled = false
        port = 8443
        keyStorePath = "keystore.p12"   # JKS or PKCS12
        keyStorePassword = "changeit"
        keyAlias = "tulpar"
        privateKeyPassword = "changeit"
    }
}

repo {
    root = "./repo-data"   # holds pool/ and the generated repodata.json
    defaultChannel = "main"
    reindexOnStart = true
}

limits {
    maxRequestsPerWindow = 120
    windowMillis = 60000
    banDurationMillis = 60000
    maxDownloadsPerIP = 4
    maxDownloadSpeed = 0   # bytes/sec, 0 = unlimited
    bufferSize = 65536
    exemptLoopback = true
}

publish {
    enabled = false
    tokens = []            # Bearer tokens for publish/delete
    validate = true
    requireSignature = false
    allowOverwrite = false
}

metrics { enabled = true, intervalMillis = 300000 }

cli {
    color = "#cccccc"
    hello = [
        "▀█▀ █░█ █░░ █▀█ ▄▀█ █▀█ ▄▄ █▀ █▀▀ █▀█ █░█ █▀▀ █▀█   ▀█ ░ █▀█",
        "░█░ █▄█ █▄▄ █▀▀ █▀█ █▀▄ ░░ ▄█ ██▄ █▀▄ ▀▄▀ ██▄ █▀▄   █▄ ▄ █▄█"
    ]
}

1. Fork the repository
2. Create a feature branch
3. Commit your changes
4. Push to the branch
5. Open a Pull Request

• 🛠 Core architecture rewrite (v2.0)
• 📦 Official plugin registry