Grayscale/nanobot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: simplify macOS launchd setup

Browse Source 
Made-with: Cursor
This commit is contained in:
Xubin Ren
2026-04-25 19:36:20 +08:00
committed by Xubin Ren
parent 8a4c338a01
commit 830211b5d4
1 changed files with 8 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/deployment.md
+8 -17
View File
@@ -95,17 +95,17 @@ If you edit the `.service` file itself, run `systemctl --user daemon-reload` bef
## macOS LaunchAgent ## macOS LaunchAgent
On macOS, run the gateway as a `launchd` user agent so it starts automatically after login and restarts if it exits unexpectedly. Use a LaunchAgent when you want `nanobot gateway` to stay online after you log in, without keeping a terminal open.
**1. Find the nanobot binary path:** **1. Get the absolute `nanobot` path:**
```bash ```bash
which nanobot # e.g. /Users/youruser/.local/bin/nanobot which nanobot # e.g. /Users/youruser/.local/bin/nanobot
``` ```
Use this absolute `nanobot` path in `ProgramArguments` so the console script keeps the Python environment from your install method. Use that exact path in the plist. It keeps the Python environment from your install method.
**2. Create the LaunchAgent plist** at `~/Library/LaunchAgents/ai.nanobot.gateway.plist` (replace paths if needed): **2. Create `~/Library/LaunchAgents/ai.nanobot.gateway.plist`:**
```xml ```xml
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
@@ -140,14 +140,6 @@ Use this absolute `nanobot` path in `ProgramArguments` so the console script kee
<key>StandardErrorPath</key> <key>StandardErrorPath</key>
<string>/Users/youruser/.nanobot/logs/gateway.error.log</string> <string>/Users/youruser/.nanobot/logs/gateway.error.log</string>
<key>EnvironmentVariables</key>
<dict>
<key>PATH</key>
<string>/Users/youruser/.local/bin:/opt/homebrew/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin</string>
<key>PYTHONUNBUFFERED</key>
<string>1</string>
</dict>
</dict> </dict>
</plist> </plist>
``` ```
@@ -155,7 +147,7 @@ Use this absolute `nanobot` path in `ProgramArguments` so the console script kee
**3. Load and start it:** **3. Load and start it:**
```bash ```bash
mkdir -p ~/.nanobot/logs mkdir -p ~/Library/LaunchAgents ~/.nanobot/logs
launchctl bootstrap gui/$(id -u) ~/Library/LaunchAgents/ai.nanobot.gateway.plist launchctl bootstrap gui/$(id -u) ~/Library/LaunchAgents/ai.nanobot.gateway.plist
launchctl enable gui/$(id -u)/ai.nanobot.gateway launchctl enable gui/$(id -u)/ai.nanobot.gateway
launchctl kickstart -k gui/$(id -u)/ai.nanobot.gateway launchctl kickstart -k gui/$(id -u)/ai.nanobot.gateway
@@ -165,11 +157,10 @@ launchctl kickstart -k gui/$(id -u)/ai.nanobot.gateway
```bash ```bash
launchctl list | grep ai.nanobot.gateway launchctl list | grep ai.nanobot.gateway
launchctl kickstart -k gui/$(id -u)/ai.nanobot.gateway launchctl kickstart -k gui/$(id -u)/ai.nanobot.gateway # restart
launchctl bootout gui/$(id -u) ~/Library/LaunchAgents/ai.nanobot.gateway.plist launchctl bootout gui/$(id -u) ~/Library/LaunchAgents/ai.nanobot.gateway.plist
log stream --process nanobot
``` ```
If you edit the plist itself, run `launchctl bootout ...` and `launchctl bootstrap ...` again so `launchd` reloads the updated definition. After editing the plist, run `launchctl bootout ...` and `launchctl bootstrap ...` again.
> **Note:** if `launchctl kickstart` fails with an "address already in use" error, you probably still have a manually started `nanobot gateway` process running on the same port. Stop the manual process first, then kickstart the LaunchAgent again. > **Note:** if startup fails with "address already in use", stop the manually started `nanobot gateway` process first.