Skip to content

Add Nixpacks configuration files to fix deployment detection error#24

Open
iamwaqargulzar wants to merge 2 commits intoessamamdani:mainfrom
iamwaqargulzar:fix-nixpacks-detection-4829662861190144067
Open

Add Nixpacks configuration files to fix deployment detection error#24
iamwaqargulzar wants to merge 2 commits intoessamamdani:mainfrom
iamwaqargulzar:fix-nixpacks-detection-4829662861190144067

Conversation

@iamwaqargulzar
Copy link

  • Added package.json to allow Nixpacks to detect the project as a Node.js application.
  • Added nixpacks.toml to configure system dependencies (Python, Go, Docker client, etc.) and build phases, mimicking the original Dockerfile setup.
  • Configured environment variables and paths to support OpenClaw execution in the Nixpacks environment.

- Added `package.json` to allow Nixpacks to detect the project as a Node.js application.
- Added `nixpacks.toml` to configure system dependencies (Python, Go, Docker client, etc.) and build phases, mimicking the original Dockerfile setup.
- Configured environment variables and paths to support OpenClaw execution in the Nixpacks environment.
- Updated `nixpacks.toml` to:
  - Add `npm install` to `phases.install` to ensure dependencies (OpenClaw) are installed.
  - Add `--break-system-packages` to `pip3 install` command to comply with PEP 668 and fix build error.
  - Make `mkdir /data` and symlink commands non-fatal to accommodate different build environments (root vs non-root).
  - Update `[start]` command to include `node_modules/.bin` and `/app/scripts` in PATH, ensuring `openclaw` binary and scripts are found at runtime.
- Verified `scripts` directory content exists.
- This resolves the "Command execution failed" error during Nixpacks build.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant