Maintainer here. Yes, the web app is a static Expo export, so the simplest self-host path is to build packages/app and serve the generated dist/ with any static HTTP server. The daemon itself is published to npm as `@getpaseo/cli`.
Docs for this are currently missing, and I should probably package all of this in a Docker image. I'll do that today!
alt Hacker News
Maintainer here. Yes, the web app is a static Expo export, so the simplest self-host path is to build packages/app and serve the generated dist/ with any static HTTP server. The daemon itself is published to npm as `@getpaseo/cli`.
Docs for this are currently missing, and I should probably package all of this in a Docker image. I'll do that today!