SoftN v0.0.29

SoftN v0.0.29

What's new

• Upgrading from v0.0.28: the engine is still ZIPP v0.0.32, so nothing is rebuilt, and the FormLogic runtime and its protocols are v0.0.28's. Studio's editor bridge reads one optional key more, aiLabel on open: FormLogic v0.1.17 sends it, and an older FormLogic's Studio says only that FormLogic's AI answers (below).
• Studio inside FormLogic says which AI it uses. Its AI is FormLogic's (every request goes to the person's default AI in FormLogic's Settings → AI), but its settings listed "FormLogic AI · FormLogic default · localhost:11434 · no key", the address of a local server it never asks, and that row's Test, its model list and its Add, Edit and Remove asked or changed a provider Studio does not use: the test and the model list failed against localhost:11434, so FormLogic's AI looked unused, and Remove left Studio with no AI until it was opened again. Now Settings shows one row, FormLogic AI with the AI FormLogic names (the editor bridge's open may carry aiLabel, one line of text, optional like saveLabel), a Test that sends a short prompt through FormLogic, and where to change it; the chat's AI pill names it too, and no longer opens a setup the hosted editor does not have. What runs learn about the AI (tool calls written as text, replies not streamed) is kept for the AI FormLogic named, so choosing another one there does not carry it over. A FormLogic that sends no label gets "Your default AI in FormLogic".

Downloads

Download	What it is	Pick it when
softn-website-v0.0.29-zipp-v0.0.32.zip	The complete softn.com website. The whole softn.com in one folder: the landing page, the app directory, the web runtime, Builder, Studio, the documentation and the directory API.	You want to run your own SoftN site: a directory people can publish apps to and play them from.
softn-app-static-v0.0.29.zip	One app on a page (static). The smallest way to host one SoftN app: a plain page with a loading spinner, a permission bar and your app, with no SoftN branding and no server code.	You have a .softn app and a web host, and you want the app on a page of your own site.
softn-app-static-with-backend-linux-x64-v0.0.29.zip	One app on a page, with an optional PHP server backend. The static single-app page above, plus a backend/ folder that lets the app run its own private server logic and SQLite database on an Apache/PHP host, with no service to keep running.	Your app has a private server part (server/ logic, SQL migrations, routes) and your host is Apache with PHP on Linux x86-64.
softn-app-private-v0.0.29.zip	One app served privately by PHP. The single-app page again, but PHP renders it and hands the app's files to the browser piece by piece behind a viewer cookie, so the .softn file itself is never at a URL.	You do not want visitors (or crawlers) to be able to download your app as one file.
softn-app-private-with-backend-linux-x64-v0.0.29.zip	One app served privately by PHP, with an optional server backend. The privately served page above together with the PHP server backend: three folders, webroot/, private/ and backend/. The app works at once without the backend; you enable the backend when the app needs it.	You want the .softn file kept off every URL and the app has a private server part.
softn-formlogic-runtime-v0.0.29.zip	The SoftN runtime for FormLogic. Everything FormLogic embeds from SoftN, already built: the sandboxed frame FormLogic runs an app in, Builder and Studio as editors inside FormLogic, the server-side runtime for native apps, and the starter adapter. FormLogic’s build downloads this from the latest SoftN release instead of building SoftN from source.	You run FormLogic and its build cannot reach GitHub; download this and point SOFTN_RELEASE_ARCHIVE at it.

Each archive unzips with a README.md at the top that explains it; RELEASE-GUIDE.md below compares them all.

The backend download targets Linux x86-64 with Apache/PHP and process execution enabled. It is a generic, unconfigured distribution: install your own public and private app bundles and preserve existing configuration, keys and databases when upgrading. Native XDB synchronization remains a Rust-host feature.

The complete website archive's name carries the tag of the zipp engine inside it. It ships no
example apps: the directory starts empty, and .softn files dropped on any
page of the site publish into it — one, or a folder at once, with the admin
key from data/config.json lifting the hourly limit for the site owner. The
example apps are published as .softn downloads with every
softn-Examples release.
The desktop loader and builder are not attached to releases; they build from
this tag's manifests with npm run tauri build in their apps. RELEASE-GUIDE.md
below compares every download and says which one to take.

The single-app archive includes a small counter example; replace it with your own bundle. It has no app download controls, but browser-delivered app bytes remain extractable. Required license notices are included in all archives.

Built with ZIPP v0.0.32 (its javascript-python-base engine, javascript engine and torch package; the release SHA256SUMS has sha256 2f54dcc6d32729814483d4d7967aa16dd2d80a37f6aa9fee6af2f4f278469876).