Guides

File download URLs

Raw source links

The Raw button uses the website URL /<owner>/<repo>:<snapshot>/raw/<path>. Choose live or a backup name. Public files need no token. Raw responses show original bytes as plain text, including HTML source.

https://brintos.io/brintos/linux:live/raw/.bashrc
https://dev-2caeefb0.brintos.io/brintos/linux:live/raw/.bashrc

Private files require a personal access token with repository read access, using Authorization: Bearer <token> or ?PAT=<token>. App-generated private Raw links contain a short-lived file grant. Add download=1&name=file.txt for an attachment.

File download grants

Request a download using a session or bearer token. Public repositories also allow anonymous reads.

GET /api/repos/<owner>/<repo>/fs/content?path=/etc/hostname&snapshot=live

The JSON response contains url, expiresAt, oid, encoding, and plaintext size. Use download=1 for an attachment, inline=1 for Raw text, or redirect=1 for an HTTP redirect. The resulting file URL uses the website's content service. A grant admits one file for 15 minutes; a healthy download can continue beyond expiry.

Download and resume

File URLs support GET, HEAD and a single byte Range, including suffix ranges. Use the ETag with If-Range. If the grant expires, renew its resumeUrl with repository authorization to preserve the original immutable file for up to four hours, even if its live path is overwritten or deleted. Transfers stream without assembling the full file in server memory.

Machine subdomains

Machine subdomains serve only the official static assets at /hardwarejs/<version>/hardwarejs.html, hardwarejs.js, and release.json. All repository file paths return 404 there. The runtime version is selected in Settings → Machine spec. Use the generated brintos.js plus iframe snippet to supply the filesystem capabilities needed to boot. See runtime selection.