Standalone Server Deployments

• Preparation
• Build
• Run
• Troubleshooting

Preparation

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.

Build

Now you can build the server with pnpm build. The backend will land as a single bundled JS file in dist/backend/index.js

Run

Running node index.js with the built file should result in your server being up. You can now deploy this file and run / manage it however you like!

Troubleshooting

If you’re having a health-check failure on deploy, steps to take to rule things out:

1. pnpm start, then open http://localhost:9001/health in a browser.
1. If you see {"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.
2. If you don’t, ensure you have completed the “Preparation” step above.
2. pnpm build
3. Change directories to dist/backend
4. Run LOGGING_LEVEL=trace node index.js
5. Open http://localhost:9001/health in a browser again.
1. If you see {"status":"ok"}, proceed to step 6. We have proven your built index.js file is able to run Fastify.
2. If you don’t, check for errors in the output from the node command. They should shed some light on what’s going on.
6. Use postman, cURL, or a similar tool to run a query. For example:

curl 'http://localhost:9001/' \
  -H 'content-type: application/json' \
  --data-raw '{"query":"query { people { name } }"}'

If this works, we know the bundled server is ready to go. Deploy to your hosting provider and run it!

If it doesn’t the output from the node command should shed some light on what’s going on.