Desktop and other origins

The application

• The first time, it asks for the address of the server’s routes and, when the server asks for one, a token, sent as Authorization: Bearer; kept, and tried again at every start.
• Server → Change Server… (⇧⌘K) asks for another.
• What it downloads goes to Downloads, a name taken made free, “report (2).pdf”.
• npm run desktop opens it against the playground; npm run build:desktop makes ReboFiles.app.

Let it in

Answered the browser’s question first, and the ETag of a part readable. Only the origins listed.

createDriveHandler({
  ...options,
  // The desktop window on a Mac and on Windows, and a page of another domain.
  cors: { origins: ['tauri://localhost', 'http://tauri.localhost', 'https://app.example.com'] },
});

And the bucket

The bytes go to the bucket from the window straight: put the same origins in its rule of origins.

Not yet

• Signing in through the server’s page, for a server whose session is only a cookie.
• Windows and Linux: built by the Desktop workflow, a .dmg, an installer of Windows, a .deb and an AppImage; not tried by hand yet. Signed and notarized when the certificates are given to it as secrets: none are yet.