Start Keystone with node <filename>.js instead of keystone start

[EkberHasanov]

I'm trying to implement graceful shutdown in a Keystone CMS running in a kubernetes pod. When a pod receives a SIGTERM signal, I want Keystone to:

Close any open database connections properly
Finish processing current requests
Exit properly

I've tried two approaches:

1. Creating a custom server.js that imports keystone.ts, creates a Keystone instance, and adds signal handlers
2. Using the Keystone CLI but wrapping it with signal handlers

The first approach consistently runs into memory issues during TypeScript compilation in our container environment. The second approach works but I don't want to do it like that. I wonder if there is a way to get keystone instance and run it in a .js file instead of keystone start command as with this approach I can easily handle sent signals.

What's the recommended way to handle graceful shutdown with Keystone? Is there a built-in way to ensure database connections are closed when the process receives a termination signals such as SIGTERM or SIGKILL?