Logseq/Entity/Asset/B2

• Backblaze B2 Asset

  • In this garden, Backblaze B2 Asset pages represent files stored in Backblaze B2, following Logseq/Entity/Asset for filenames, ownership, and page contents.

  • Storage location

    • Upload the page-derived filename at the root of the garden's configured B2 bucket. Its optional local copy uses assets/.remote/<filename>.
    • For Course/Asset/Diagram/Overview/png, the filename is Course___Asset___Diagram___Overview.png and the local copy is assets/.remote/Course___Asset___Diagram___Overview.png.
    • Public uploads use the S3 endpoint returned by B2 authorization: https://<s3-host>/<garden-bucket>/Course___Asset___Diagram___Overview.png. The garden's B2 configuration supplies the host and bucket; URL encoding preserves the filename.
    • Private uploads retain the authenticated B2 download URL, https://<download-host>/file/<garden-bucket>/<filename>.

  • Frontmatter and body

    • A B2 asset carries logseq-entity:: [[Logseq/Entity/Asset/B2]]. Shared asset frontmatter and embedded media or download links follow Logseq/Entity/Asset.
    • The body uses the usable remote URL. The URL already identifies the bucket and filename; separate properties would repeat them.

  • Uploading and backing up

    • Uploading makes a file available at its remote location. Publication through a website or podcast feed is a separate step in that site's workflow.
    • DVC maintains checksums and restoration metadata separately. A DVC push backs up a tracked file; a named B2 upload supplies the URL used by its asset page.
    • Asset/mise/Task/add tracks the page-named working file; Asset/mise/Task/push backs it up and Asset/mise/Task/fetch restores it. GitP/mise/Task/media/upload uploads and verifies the named object used by the page.