slop-GmbH/slopcut
Watch
1
0
Fork
You've already forked slopcut
 0
Code Issues Pull requests Projects Releases 5 Packages 1 Wiki Activity Actions
5 releases 6 tags
  • v0.1.0-beta.4 681eb112f7

    v0.1.0-beta.4 Pre-release

    niico released this 2026-10-26 22:17:03 +00:00 | 25 commits to dev since this release

    SlopCut 0.1.0-beta.4: in-app updates, automatic server certificates, Pelican egg

    The app can now update itself. The server gets its own Let's Encrypt certificate and can be hosted with a
    Pelican egg. This release also fixes server self-update, which never worked before.

    Mobile App

    Features

    • Opt-in update check. On first launch the app asks once whether it may check for updates; Settings has
      a switch to change the answer. When on, the app asks git.slopmc.net for new releases at most once a
      day. The request carries no identifiers. While off or offline, the app makes no request.
    • When a newer release exists for your channel, an "Update" button appears in the top bar. A beta build
      is offered betas and stable releases; a stable build only stable releases. Tapping it downloads the
      APK, checks its SHA-256 against the release's SHA256SUMS and hands it to Android's installer.
      Android asks you to confirm and installs only an APK signed with the same key. The downloaded file is
      deleted afterwards.
    • New Settings screen (gear icon in the project list): update check switch and app version.
    • This is the app's first network access: it now holds the INTERNET permission. The only connection
      is HTTPS to git.slopmc.net, verified with the system's certificate authorities.

    Fixes

    • None.

    Known issues

    • On the first update, Android asks you to allow "install unknown apps" for SlopCut.
    • Debug builds do not update themselves (separate package and signing key).
    • No accounts or cloud saves yet.

    Server

    Features

    • Automatic certificates. Set SLOPCUT_TLS_DOMAIN=cut.example.com instead of cert/key files, and the
      server gets and renews a Let's Encrypt certificate by itself (ACME TLS-ALPN-01). It needs no secret or
      upload, and it swaps a renewed certificate in without a restart. Port 443 of the domain must reach the
      server: with Docker, map "443:8443"; if 443 is already in use, add a TLS passthrough (SNI) rule.
      SLOPCUT_TLS_ACME_DIRECTORY switches to Let's Encrypt staging for a first try.
    • Pelican egg egg-slopcut-server.yaml, attached to this release. The installer checks the binary
      against SHA256SUMS, and every setting is a validated panel variable. A guide covers DNS and SNI
      passthrough when the node already uses 443: server/deploy/pelican/README.md.

    Fixes

    • Self-update could never stage an update. Every download of the 64-byte update signature failed with
      "the response body is larger than request limit: 64". On the dev branch this also logged a warning
      at every check.

    Known issues

    • Servers on 0.1.0-beta.3 or older cannot update themselves to this version, because the bug above is in
      the old binary. Update once by hand: with Docker, download this release's docker-compose.yml and run
      docker compose pull && docker compose up -d. After that, self-update works.
    • Switching an existing install to SLOPCUT_TLS_DOMAIN needs this version as the image or installed
      binary, not only as a self-update.
    • The Pelican egg is not yet confirmed on a real Wings node.
    • Behind a passthrough proxy the server sees the proxy's IP address. This has no effect until accounts
      exist.
    • No accounts or cloud saves yet; the server serves /v1/health and updates itself.

    Server image: git.slopmc.net/slop-gmbh/slopcut-server:0.1.0-beta.4@sha256:9fdc5b78dfebe56c4ff5fc6e761c7bbf35b134d6984c02a8397ec1256b1df586 (see docker-compose.yml).
    Pelican egg import URL: https://git.slopmc.net/slop-GmBH/slopcut/raw/branch/beta/server/deploy/pelican/egg-slopcut-server.yaml

    Downloads