Polari Apps

Ordinary web apps: pages, data and simulations that run on your isle's Polari.

searching Polari Apps
Materials & DevicesMaking & MechanicsFood & LivingEnvironment & BioBusiness & WorkKnowledge & MediaPlatform & Operationsclear

3 app(s) match in Polari Apps.

  1. Bizops bizops polari-app

    Business operations: setup/upgrade flows, local-economy track, order planner with mold-ladder reuse.

    Polari Apps · Business & Work — operations, orders app payload 152.6 KB · no extra libraries · needs modules: supplychain steps on download: analyze shared payload → package module files → write manifest → assemble deb → stream to you the offline install form carries the pip libraries inside the deb
    Install — runs hereThe app itself, for host / hardware members.Generated fresh when you click, then removed from the server after delivery. usually ~0.8 s to generateGenerate & download
    Access only — the shellOpens the app hosted on your isle; installs nothing else. For any member, even Access only. Offline: carries the shell runtime when the core staged it.READY — generated 0 min ago, held at least 10 more min (requested 1×, downloaded 0×) · 52.2 MB · download usually ~3.8 sDownload
    DEV Dev variantOffered on dev-posture instances only (this one is in production posture). The same app with security observing — warns, never denies; for testing on your own isle.
  2. Collab collab polari-app

    Collaboration sessions (mtg-2, LIVEKIT_COLLABORATION_PLAN v2): one session object, many client surfaces (browser meeting, sim-side voice, VR). CollaborationSession + MeetingRecord rows; KC-verified callers mint short-lived LiveKit JWTs (pure-stdlib HS256 — no SDK); capability/join-info with the *_remote refusal ladder. THE LINE: nothing arriving over LiveKit mutates Polari state. Second module born manifest-first on dyn-1.

    Polari Apps · Business & Work · Knowledge & Media — meetings, livekit app payload 76.1 KB · 1 library (3.5 MB measured) steps on download: analyze shared payload → package module files → write manifest → assemble deb → stream to you the offline install form carries the pip libraries inside the deb
    Install — runs hereThe app itself, for host / hardware members.Generated fresh when you click, then removed from the server after delivery. usually ~8 s to generateGenerate & download
    Access only — the shellOpens the app hosted on your isle; installs nothing else. For any member, even Access only. Offline: carries the shell runtime when the core staged it.Generated fresh when you click, then removed from the server after delivery. usually ~5.2 s to generateGenerate & download
    DEV Dev variantOffered on dev-posture instances only (this one is in production posture). The same app with security observing — warns, never denies; for testing on your own isle.
  3. Odooconnect odooconnect polari-app

    Odoo ERP connector: JSON-RPC client with sim/ops write guards, instance configs, /api/odoo status.

    Polari Apps · Business & Work · Bridges & Integrations — odoo, erp app payload 137.2 KB · no extra libraries · needs modules: bizops, supplychain steps on download: analyze shared payload → package module files → write manifest → assemble deb → stream to you the offline install form carries the pip libraries inside the deb
    Install — runs hereThe app itself, for host / hardware members.READY — generated 70 min ago, held at least 2 more min (requested 1×, downloaded 1×) · 35.9 KB · download usually <1 sDownload
    Access only — the shellOpens the app hosted on your isle; installs nothing else. For any member, even Access only. Offline: carries the shell runtime when the core staged it.READY — generated 1115 min ago, held at least 3 more min (requested 1×, downloaded 1×) · 52.2 MB · download usually ~3.8 sDownload
    DEV Dev variantOffered on dev-posture instances only (this one is in production posture). The same app with security observing — warns, never denies; for testing on your own isle.

Installing

  1. Click Generate & download (or Download when it is already made) on the form you want; the card says how long it usually takes.
  2. If the card lists a shared-payload file, install that one first.
  3. Double-click the downloaded file and choose Install. An Install form stages the app for the isle to admit; an Access form is a launcher that finds and opens the app your isle hosts.

What is all this?

What is a .deb file?

The standard installer format on Ubuntu and other Debian-family Linux — the equivalent of a setup file on other systems. Your computer's own Software Install app reads it, shows what will be installed, and asks for your password through the system dialog. Nothing runs until you approve it.

Online deb vs offline deb — which do I want?

Online is small: it carries the app itself, and the libraries it needs are fetched from the internet when the app is set up — each card lists those libraries and their measured sizes, so nothing downloads invisibly. Offline carries the pip libraries INSIDE the deb (bigger, slower to generate — wheels are fetched at build time), for machines that will have no internet. System engines (e.g. a SPICE simulator) can never ride inside an app deb — they come from the distro's packages or the offline install media, and each card names them.

Why is there a short wait after I click?

These debs are not kept on the server — each one is packaged fresh at the moment you ask (analyze shared payload → package module files → write manifest → assemble deb → stream to you), then kept at least three slow-connection downloads long, then only evicted when room is needed, and freed after a day untouched. The wait shown on each card is the median of that app's recorded generation times — measured, never invented.

What do "pre-prepped" and "generated on demand" mean?

Pre-prepped files are built ahead of time and sit ready on this server, so the download starts instantly. Generated on demand files are packaged fresh at the moment you ask for them — you wait briefly while the server builds your copy, and the server deletes its copy after delivery instead of keeping a duplicate on disk. Each item on these pages says which kind it is.

What are the "shared payload" files some apps mention?

When two apps contain identical files, those files are factored into one shared deb both apps depend on, so the content installs exactly once — the installer enforces it. Install the shared deb first; each app card links it when it applies.

How does an installed app become live?

Installing an app deb stages its code and data under /var/lib/polari/apps/. The running instance admits staged apps through the dynamic-modules machinery, which is still in review — until it lands, an administrator has to admit the module on the instance manually. This page will say so until that changes; nothing happens invisibly.

What ends up on my disk, and where?

Programs install into the system software areas (/usr, /opt) and app data lives under /var/lib/polari. The .deb file you downloaded is only the delivery vehicle — once the install finishes it is safe to delete from your Downloads folder.

← Install Polari itself: the platform installers, online and offline, and the USB stick.