v0.1.2
Run a command in an app from its page, update Ferrum from the Updates card, and Redis instances start.
What's New
- A Run tab on every app that has a process. Type a command and it runs in the app's current release, as the app's user, with the app's environment and toolchain, under the build memory limit and the migration time limit. The output streams live and the last 20 runs stay on the tab with their result.
- Update now on the Updates card in Settings, next to Check now.
- After an update, the tab reloads by itself once the new build answers.
- Redis is set up with
vm.overcommit_memory = 1, as Redis recommends, when it is installed and when Ferrum starts.
Bug Fixes
- A Redis instance requested for an app never started: its configuration named the append-only directory with the wrong directive, and Redis refused the file. Instances made before this release are corrected and started when Ferrum starts.
- Requesting Redis reported success even when Redis exited right after starting. The request now fails with the last lines of the instance's log and leaves nothing behind.
- The update banner could sit above the visible page. It now stays inside the page frame on desktop and inside the header on phones.
Update
From the panel: Settings → Updates → Update now, or ferrum update on the server. A fresh install:
curl -fsSL https://raw.githubusercontent.com/irixsoft/ferrum/main/install.sh | sudo shVerify
Every release ships ferrum-x86_64-unknown-linux-musl, ferrum-aarch64-unknown-linux-musl, SHA256SUMS, SHA256SUMS.sig and ferrum-pub.pem. The installer and the updater check them; by hand:
openssl pkeyutl -verify -pubin -inkey ferrum-pub.pem -rawin -in SHA256SUMS -sigfile SHA256SUMS.sig
sha256sum -c SHA256SUMS --ignore-missing