Skip to main content

CesiumCloud v0.2.0

CesiumCloud stores files as independently deletable physical storage objects. New uploads do not use shared multi-file packs, and renaming or deleting one file does not rebuild unrelated files.

Service: https://cloud.cesiummc.space/app/ API: https://api.cesiummc.space Transfer endpoint: https://transfer.cesiummc.space

CLI

Authenticate with cesiumcloud authenticate. Your credentials are local and can be revoked.

  • cesiumcloud upload "path/to/file-or-folder"
  • cesiumcloud list -a
  • cesiumcloud search notes.txt
  • cesiumcloud dir images
  • cesiumcloud download "restore-directory"
  • cesiumcloud download images/photo.png --location "restore-directory"
  • cesiumcloud rename old.txt new.txt
  • cesiumcloud move old.txt to root/archive
  • cesiumcloud delete root/archive/old.txt

Uploads transfer in resumable 64 MiB chunks using a short-lived authorization grant. Individual files can be downloaded, replaced and permanently removed from active storage without rebuilding other files.

JavaScript SDK

const { IsolatedTransferClient } = require("cesiumcloud");
const storage = new IsolatedTransferClient(process.env.CESIUMCLOUD_API_KEY);
await storage.uploadFile("notes.txt", "docs/notes.txt");
const files = await storage.allFiles();
await storage.download(files[0].id, "./restored.txt");
await storage.delete(files[0].id);

Python SDK

import os
from cesiumcloud import IsolatedTransferClient
storage = IsolatedTransferClient(os.environ["CESIUMCLOUD_API_KEY"])
storage.upload_file("notes.txt", "docs/notes.txt")
files = storage.all_files()
storage.download_file(files[0]["id"], "restored.txt")
storage.delete_file(files[0]["id"])

Existing CesiumCloudClient high-level upload and download methods also use isolated file storage.

Optional local encryption

Use cesiumcloud e2ee keygen to generate a local recovery key, and cesiumcloud e2ee upload FILE to encrypt locally before upload. The server cannot recover your key. Keep an offline backup. Encryption protects contents, not filenames or sizes. The .ccenc format is authenticated and cross-platform.

Notes

Deletion removes the active storage object, not necessarily historical provider backups or copies you exported. Interrupted uploads can be resumed while their authorization and session remain valid. Keep offline backups of important data. This release does not automatically migrate old shared-pack archives.

Replacement and upload cancellation (0.2.1)

Use cesiumcloud upload --replace "file.txt" (or a folder) to replace a matching virtual path, or create it normally when absent. The SDK accepts replace=True in upload_file and upload_path and has cancel_upload(upload_id). Use cesiumcloud cancel-upload UPLOAD_ID or Ctrl+C on an active CLI upload. Already completed files are preserved. The website's ReplacedFiles history is separate from the CLI flag.

Version 0.2.10

The dir command validates its destination against the authenticated server catalog, including explicitly created empty folders. Deleted and trashed directories are rejected even when another terminal or browser tab still has an old folder view. The server rejects new uploads to invalid directories at both upload admission and file commit.

0.2.11: rolling independent-file uploads

Directory navigation remains authenticated against the server, including empty folders, with trashed or deleted destinations rejected. Uploading folders and multi-source selections now defaults to up to 40 simultaneous uploads while preserving the per-file storage model and the shared Altare global admission queue. The first set of 40 independent upload reservations is registered and transfers start immediately; subsequent registrations overlap with active transfers rather than blocking on admission for every selected file. Explicit -simultaneous N retains concurrency control, capped at 40 for uploads. Single-file uploads retain their live progress behavior. Incremental aggregate byte counters and throttled terminal refreshes avoid rescanning thousands of entries per update. Unused reservations are cancelled on interruption or partial failure.

Metadata

Release files for cesiumcloud 0.2.12

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for cesiumcloud 0.2.12
File Size Uploaded Provenance Actions
cesiumcloud-0.2.12.tar.gz 62.8 kB With provenance Details for cesiumcloud-0.2.12.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for cesiumcloud 0.2.12
File Interpreter ABI Platform Actions
cesiumcloud-0.2.12-py3-none-any.whl Python 3 none any Details for cesiumcloud-0.2.12-py3-none-any.whl

Total release size: 111.5 kB

Release files / cesiumcloud-0.2.12.tar.gz

Download URL cesiumcloud-0.2.12.tar.gz
Size 62.8 kB
Tags Source
SHA-256 checksum
How to use checksums
3eb2af2f5d633d18046ea805b56400935eeedd915e1595b7015bbea1613ceecb
BLAKE2b-256 checksum
How to use checksums
d06145ab892143864b9e33870c9fdec1ef399f59a97fd212f0ecd0d741721bdf
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 1, 2026.

Transparency log

Release files / cesiumcloud-0.2.12-py3-none-any.whl

Download URL cesiumcloud-0.2.12-py3-none-any.whl
Size 48.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
3636d5a849b7369b667637be0706c914db67afd17576dac5abca27b8a7cd9248
BLAKE2b-256 checksum
How to use checksums
8f0bdc6c9a163d2f5fd63dc546cc9a79e44e09ef4c5175a78d2d0c741f74d78f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 1, 2026.

Transparency log

Security for cesiumcloud 0.2.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for cesiumcloud-0.2.12.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 1, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.2.12 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page