Docker + FrankenPHP

[brendt]

So my vision is that we ship a Docker container with Tempest that's ready for development and production use. I'm of the opinion that it should have FrankenPHP as the default runtime.

I think this issue will require a couple of steps:

• Make a working Docker image for Tempest as it is right now (with FrankenPHP, but without worker mode)
• Make the necessary changes in the framework to support worker mode

I'm happy to work on the second step, but for the first step we'll need help. I'm assigning @aidan-casey for now, but let's first discuss a proper plan in this issue.

[iamdadmin]

Summarising the node <> tempest interactions when using the vite plugin

From node TO tempest

• tempest/vite-plugin-tempest needs to execute php tempest vite:config however this also has a manual override where the config file can be provided directly.

• It does this when you first install the plugin but once created, it would be added to your git repo, and thus a prod web server doesn't need to create it.

• On a local dev machine even if using frankenphp to serve the PHP portion, you'll have cli access to the folder and be running the jsweb stack install on your local console anyway. I don't think anyone runs interactive docker to do the installs inside in this situation?

• On a Prod web server you'd use the existing file as committed to the git repo and not need to create it from scratch i.e. node and php would not need to co-exist in the same single container as they wouldn't issue each other commands.

• On a Prod web server with a static SSR bundle, you'd not need any active bundler so no need for node to be in the same container.

• On a Prod web server where you're using SFA or hydrating a bundle for the front end, you could just as easily have a separate node container since the interaction would be over TCP ports at this level, once that first time config file is created.

From tempest TO node

• tempest/vite installer can scaffold package.json and run an initial bun install to install dependencies.

• Once this is done, there doesn't seem to be any further need for Tempest to run node commands.

• Again on a local dev machine you'd have console access, and just be using frankenphp to serve the PHP portion, so this initial installer would be performed there, and the artifacts part of the repo.

• On a Prod web server, you would need to bun install the dependencies since of course that's not synced in the git repo, however that can be run via the node container without dependency on PHP or tempest as far as I can tell, once the installers have run.

Summary

Please do correct me if I've misunderstood any of the above, but if I have understood it correctly, essentially once the install is done and the scaffolded files exist, there's no technical requirement for tempest or jsweb to pass each other commands and thus no requirement to run both within the same container. That also has the benefit of us not having to constantly update the container for node releases, as it can just be a node:latest separate container.