Files
feedc0de 5bb6e0fe55
Check source / check (push) Successful in 16s
Initial version (not finished, work in progress)
2026-11-18 10:10:39 +01:00

2.5 KiB

Gitea Actions

The repository is hosted at https://code.brunner.ninja/feedc0de/mikrotik-olsr.

Enable Actions and provide a trusted Linux runner with the ubuntu-latest label, Python 3.12 or later, passwordless sudo for the listed build dependencies, and network access to the pinned source/toolchain hosts and official MikroTik downloads. The check workflow needs no signing credentials and runs on pushes and pull requests.

Secrets

Generate a dedicated release keyset locally:

python tools/routeros.py keygen --output .keys/release.json
python tools/routeros.py public-key --keys .keys/release.json --output release-public-key.json

In repository Settings -> Actions -> Secrets, add:

  • MIKROTIK_SIGNING_KEYSET: the complete contents of .keys/release.json.
  • GITEA_RELEASE_TOKEN: a token authorized to create releases and upload assets for this repository, with the minimum applicable repository-write permissions.

Back up the release keyset outside the runner. Do not generate new release keys on each run: installed devices must recognize future packages. Protect main and limit who can modify/run the release workflow. Do not run untrusted pull request code with release secrets.

The signing step writes the key to a private temporary file and removes it on exit. Only the public key export is included in the release output.

Run a release

Run Build experimental release manually on main, selecting the RouterOS version and a new tag such as ros-7.25.1-arm-r1. The workflow builds BusyBox/OLSR payloads, patches/signs packages and both installers, verifies signatures, and uploads a Gitea prerelease.

The uploader first creates a draft, uploads all checksummed files, and only then publishes it. A failed upload leaves a draft for inspection. It never overwrites an existing release tag automatically.

No signing secret or release token is shipped with this repository. Until those secrets and a runner are configured, the workflow definition alone cannot produce a hosted release. Hardware validation is not performed by CI, and the prerelease description explicitly records the unfinished OLSR integration.

Download page

The buildless page in site/ fetches public release metadata from the Gitea API. Host that directory on your static web server. The server must allow browser access to the public Gitea API (CORS for a different origin). The page also links directly to Gitea releases when API access is unavailable. No private token belongs in the page.