The best way to control Claude Code, Codex and more from any computer or phone
Mirrored from https://github.com/Camo67/t3code.git
Synced Nov 21, 04:45 UTC
| 1 | import { DockerLive } from "@alchemy.run/docker/Docker"; |
| 2 | import type * as RpcServer from "alchemy/Local/RpcServer"; |
| 3 | /** |
| 4 | * The AWS provider group served by the dev sidecar (see |
| 5 | * `Local/Sidecar.ts`): the floci-backed local providers, whose long-lived |
| 6 | * state — `Bundle.watch` loops hot-swapping Lambda code into the emulator, |
| 7 | * ECS image watch loops rebuilding and restarting task containers — |
| 8 | * survives exec-process hot reloads during `alchemy dev`. Built per session |
| 9 | * the first time a stack asks for one of their types, so a stack without |
| 10 | * AWS resources never starts the emulator. Mirrors |
| 11 | * [Cloudflare/Local.ts](../../Cloudflare/Local.ts). |
| 12 | */ |
| 13 | import * as Layer from "effect/Layer"; |
| 14 | import { FlociServiceProvider } from "../ECS/FlociServiceProvider.ts"; |
| 15 | import { FlociTaskProvider } from "../ECS/FlociTaskProvider.ts"; |
| 16 | import { FlociFunctionProvider } from "../Lambda/FlociFunctionProvider.ts"; |
| 17 | import { FlociMicrovmImageProvider } from "../Lambda/FlociMicrovmImageProvider.ts"; |
| 18 | |
| 19 | export default Layer.mergeAll( |
| 20 | FlociFunctionProvider(), |
| 21 | FlociMicrovmImageProvider(), |
| 22 | FlociTaskProvider(), |
| 23 | FlociServiceProvider(), |
| 24 | ).pipe( |
| 25 | // The ECS image pipelines (docker build / mirror / push) run in the |
| 26 | // sidecar and need the Docker CLI service. |
| 27 | Layer.provide(DockerLive), |
| 28 | ) satisfies RpcServer.ProviderLayer; |