The concept of a "nextjs webapp" like "vercel in a box" didn't pan out because it turns out that nextjs is inextricably bound to Vercel and really can't be used in the way we aimed at using it. Also it changes week to week and is maintained by crazy people.
So...we should double back and see if we can first implement support for some sort of generic webapp-like functionality.
The idea would be to take any/most git repositories that contain some JS/TS code that runs unded node/bun/thing-du-jour and transparently containerize it.
Change the name to "app" rather than "webapp"? Or perhaps "webapp" is ok still?
Inject the config/scripting needed to make such a repo run, which is typically some environment variables, some concept of the http url it is serving, a script that runs "npm server" or whatever.
The concept of a "nextjs webapp" like "vercel in a box" didn't pan out because it turns out that nextjs is inextricably bound to Vercel and really can't be used in the way we aimed at using it. Also it changes week to week and is maintained by crazy people.
So...we should double back and see if we can first implement support for some sort of generic webapp-like functionality.
The idea would be to take any/most git repositories that contain some JS/TS code that runs unded node/bun/thing-du-jour and transparently containerize it.
Change the name to "app" rather than "webapp"? Or perhaps "webapp" is ok still?
Inject the config/scripting needed to make such a repo run, which is typically some environment variables, some concept of the http url it is serving, a script that runs "npm server" or whatever.