IronClaw: Extra configuration during install to ensure Web Gateway can run#14635
Merged
MickLesk merged 6 commits intoMay 23, 2026
Merged
Conversation
MickLesk
requested changes
May 22, 2026
…etion gateway line
michelroegl-brunner
approved these changes
May 22, 2026
MickLesk
approved these changes
May 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
✍️ 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.
🔗 Related Issue
Fixes #13983
✅ Prerequisites (X in brackets)
🛠️ Type of Change (X in brackets)
README,AppName.md,CONTRIBUTING.md, or other docs.