close
Skip to content

IronClaw: Extra configuration during install to ensure Web Gateway can run#14635

Merged
MickLesk merged 6 commits into
community-scripts:mainfrom
SystemIdleProcess:fix/ironclaw-gateway
May 23, 2026
Merged

IronClaw: Extra configuration during install to ensure Web Gateway can run#14635
MickLesk merged 6 commits into
community-scripts:mainfrom
SystemIdleProcess:fix/ironclaw-gateway

Conversation

@SystemIdleProcess
Copy link
Copy Markdown
Contributor

@SystemIdleProcess SystemIdleProcess commented May 21, 2026

✍️ Description

Using default install of both debian and alpine I could not get onboard to run without db_error after final prompt and when I did get it to work using onboard --quick I could not get the gateway to start no matter were I set the values to enable it. After much trial and error I found that the .env can easily get a IRONCLAW_PROFILE=local value. Looking to nearai\ironclaw repo I found that this enables cli and disabled gateway. We can set the values needed in the .env, on the service (debian) and in the database using ironclaw config set commands. I added some clarifying steps and outputs for post install steps also. I think they are okay and meet standards. If you feel that this change is not needed or the extra steps are cumbersome I understand if you do not wish to merge it. But I had to have an install that worked. I only have local Ollama so could not test configuring some during onboard but I've tested the actual install over and over.

  • Add more post setup messaging for "Next Steps"
  • Debian pull gnu binary
  • Store gateway auth key in creds file
  • Add all gateway and database related values to environment file and service file (debian only)
  • Update database using ironclaw config set to store gateway config
  • Clear secret from .env so Environment can be properly chosen during onboard

🔗 Related Issue

Fixes #13983

✅ Prerequisites (X in brackets)

  • Self-review completed – Code follows project standards.
  • Tested thoroughly – Changes work as expected.
  • No security risks – No hardcoded secrets, unnecessary privilege escalations, or permission issues.

🛠️ Type of Change (X in brackets)

  • 🐞 Bug fix – Resolves an issue without breaking functionality.
  • New feature – Adds new, non-breaking functionality.
  • 💥 Breaking change – Alters existing functionality in a way that may require updates.
  • 🆕 New script – A fully functional and tested script or script set.
  • 🌍 Website update – Changes to script metadata (PocketBase/website data).
  • 🔧 Refactoring / Code Cleanup – Improves readability or maintainability without changing functionality.
  • 📝 Documentation update – Changes to README, AppName.md, CONTRIBUTING.md, or other docs.

@github-actions github-actions Bot added bugfix update script A change that updates a script labels May 21, 2026
@SystemIdleProcess SystemIdleProcess marked this pull request as ready for review May 21, 2026 23:03
@SystemIdleProcess SystemIdleProcess requested a review from a team as a code owner May 21, 2026 23:03
Comment thread install/ironclaw-install.sh Outdated
Comment thread install/ironclaw-install.sh Outdated
Comment thread install/ironclaw-install.sh Outdated
Comment thread install/ironclaw-install.sh Outdated
Comment thread install/alpine-ironclaw-install.sh Outdated
@MickLesk MickLesk merged commit a73aefa into community-scripts:main May 23, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bugfix update script A change that updates a script

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants