If you want to deploy to Docker without using CDK, the first step is to ensure the handler export is removed from the backend/index.ts file. Our projects add a line in that looks like this:
// Remove this line!
export const handler = graphweaver.handler();
This is what tells Graphweaver to use Lambda as the deployment target.
Once you’ve removed that line, you’ll be running in Fastify, both locally and when you build.
Running graphweaver build will produce dist/backend/index.js , which you can run directly with node . For example:
Dockerfile
# Use the official Node.js image as the base
FROM node:20
# Set the working directory within the container
WORKDIR /usr/src/app
# Copy the application code from the specified directory
COPY ./ ./
# Expose the port your app will run on (e.g., 9001)
EXPOSE 9001
# Run the application (replace with your actual command)
CMD ["node", "index.js"]
It is common to need a Health Check. Once you’re running in Fastify mode (e.g. you’ve completed the step in the Preparation step above), a health check is available at http://localhost:9001/health which will return status 200 with a body of:
{"status":"ok"}
If you’re having a health-check failure on deploy, steps to take to rule things out:
pnpm start, then open http://localhost:9001/health in a browser.
{"status":"ok"}, kill the server with Ctrl-C and proceed to step 2. We have proven that your Graphweaver instance is running in Fastify mode.pnpm builddist/backendLOGGING_LEVEL=trace node index.js{"status":"ok"}, kill the server with Ctrl-C and proceed to step 6. We have proven your built index.js file is ready to go into the Docker container.