t3-code-android-nightly/.repos/alchemy-effect/examples/fly-website-solidstart/README.md

1.4 KiB

Fly Website: SolidStart

Deploys a SolidStart site to Fly with Fly.Website.SolidStart — no adapter setup in the project config.

The Node adapter bundle runs as a Fly Service on a Machine (port 3000).

  • src/routes/index.tsx is server-rendered on the Fly Machine and reads GREETING from process.env.
  • A Tailwind-styled Card component ships with the page.
  • vite.config.ts holds only solidStart() and the Tailwind plugin — no nitroV2Plugin(); the deploy target owns the nitro plugin instance.
  • Static assets under public/ (or static/) deploy with the service.
const site = yield* Fly.Website.SolidStart("Website", {
  env: { GREETING: "Hello from SolidStart on Fly!" },
});

The integration package must be installed in the project (it is loaded dynamically at deploy time), alongside @solidjs/vite-plugin-nitro-2:

bun add -d @alchemy.run/frontend-frameworks
bun add @solidjs/vite-plugin-nitro-2

Deploy

bun install
bun run deploy

Unchanged sources skip the build entirely on subsequent deploys — the input files are content-hashed (scoped by memo.include).

Dev

bun run dev

alchemy dev runs the framework's own dev server (HMR included) and no cloud resources are created. SolidStart 2's dev server (via srvx/node) misrenders under Bun, so run alchemy dev with Node for this example.

Destroy

bun run destroy