Object storage
Object storage is useful for release assets, static site files, archives, installers, screenshots, and internal distribution bundles.
1. Package or build the asset
Use a manifest-backed artifact whenever possible:
fission package --project-dir . --target linux --format run --release
fission package --project-dir documentation --target static-site --format static --release
2. Configure the destination
The provider configuration should name the bucket or container, prefix, public-link policy, cache headers, content-type behavior, and credential reference. Long credentials do not belong in fission.toml.
3. Publish
fission publish \
--project-dir . \
--provider s3 \
--artifact target/fission/release/linux/run/artifact-manifest.json \
--site production
The upload should preserve MIME types from the manifest and record public or private links in the receipt.
4. Verify access
Check the exact uploaded objects:
fission distribute status \
--project-dir . \
--provider s3 \
--artifact target/fission/release/linux/run/artifact-manifest.json \
--site production
With --artifact, Fission checks the object keys planned from the manifest and
reports whether they are present, partially present, or missing. Confirm cache
headers, content type, size, hash, and access policy before sharing the link.
Fission
A cross-platform, GPU-accelerated user interface framework for Rust. MIT licensed.
Copyright (c) 2026 Fission
Ready to use today. Widget APIs are expected to remain stable; some runtime and shell APIs may change before 1.0.0.
Fission 0.7.0