Skip to content

Complete source examples

Each project needs one backend.fast file. These downloads derive from the committed example sources, with checksums in source.json. The examples use the supported compiler subset. Do not treat a short excerpt elsewhere as a complete project.

Models, authenticated writes, ownership, GET caching and event emission.

Terminal window
mkdir -p my-counter
curl -fsS https://docs.backend.fast/examples/simple-counter/backend.fast \
-o my-counter/backend.fast
bfast deploy --name my-counter --tier small ./my-counter

Read Counter source. The quickstart supplies users, protected requests, update and deletion. The optional Python client prompts for the app password and keeps credentials in memory.

Typed inputs, validated strings, query filters, update paths and app auth.

Terminal window
mkdir -p my-links
curl -fsS https://docs.backend.fast/examples/url-shortener/backend.fast \
-o my-links/backend.fast
bfast deploy --name my-links --tier medium ./my-links

Read Shortener source. After creating an app user, use POST /links with a slug, target URL and title. The /r/:slug route returns target data as JSON; it does not follow an HTTP redirect.

Tickets, comments, private attachments, event handlers, once receipts and a daily job.

Terminal window
mkdir -p my-desk
curl -fsS https://docs.backend.fast/examples/minidesk/backend.fast \
-o my-desk/backend.fast
bfast deploy --name my-desk --tier small ./my-desk

Read Minidesk source. Use the generated TypeScript client for File transfer. Inspect work through events and jobs.

Choose fresh deployment names. Keep each source’s declared DSL app name unchanged when updating an existing app. Your display name and random hostname are separate.