In a monorepo, each deployable app has its own .hx in its package directory (e.g. packages/api/.hx). hx looks for .hx in the current working directory, so commands invoked from anywhere other than that directory fail with "local Hyphen app config is missing or incomplete."
This is a real constraint for monorepo Docker deploys: the build context needs to be the repo root so the image can see the workspace lockfile, which means hx deploy runs from the root — where there's no .hx.
It would be great if hx natively supported monorepos so a single deploy invocation could find the right app config without per-package working-directory gymnastics or copying .hx around. Ideally, the new format would support multiple apps in the repo within a single Hyphen project.
In a monorepo, each deployable app has its own
.hxin its package directory (e.g.packages/api/.hx).hxlooks for.hxin the current working directory, so commands invoked from anywhere other than that directory fail with "local Hyphen app config is missing or incomplete."This is a real constraint for monorepo Docker deploys: the build context needs to be the repo root so the image can see the workspace lockfile, which means
hx deployruns from the root — where there's no.hx.It would be great if
hxnatively supported monorepos so a single deploy invocation could find the right app config without per-package working-directory gymnastics or copying.hxaround. Ideally, the new format would support multiple apps in the repo within a single Hyphen project.