Compare commits
1 Commits
v0.2.0
...
31c7e254ab
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
31c7e254ab |
@@ -192,6 +192,48 @@ If opencode sessions become out of sync:
|
||||
2. `kugetsu prune` removes orphaned files
|
||||
3. For full reset: `kugetsu destroy --base -y && kugetsu init`
|
||||
|
||||
## Remote Access via SSH (Optional)
|
||||
|
||||
To access kugetsu from a remote machine, SSH setup is required.
|
||||
|
||||
### Automated Setup
|
||||
|
||||
Run the SSH setup script inside your container:
|
||||
|
||||
```bash
|
||||
bash skills/kugetsu/scripts/sshd-setup.sh <username>
|
||||
```
|
||||
|
||||
Omit `<username>` to use default user `kugetsu`.
|
||||
|
||||
### What It Does
|
||||
|
||||
- Checks systemd prerequisite
|
||||
- Creates non-root user
|
||||
- Configures SSH for key-only authentication
|
||||
- Enables passwordless sudo for the user
|
||||
- Starts sshd via systemd
|
||||
|
||||
### After Setup
|
||||
|
||||
1. Add your SSH public key to `~/.ssh/authorized_keys` on the container
|
||||
2. Configure port forwarding on the host (see [docs/kugetsu-setup.md](../../docs/kugetsu-setup.md))
|
||||
3. Connect: `ssh -p 2222 <username>@<host-ip>`
|
||||
|
||||
### Remote Usage
|
||||
|
||||
Once connected via SSH, kugetsu works the same as local:
|
||||
|
||||
```bash
|
||||
kugetsu list
|
||||
kugetsu start github.com/shoko/kugetsu#14 "fix bug"
|
||||
kugetsu continue github.com/shoko/kugetsu#14
|
||||
```
|
||||
|
||||
### Documentation
|
||||
|
||||
See [docs/kugetsu-setup.md](../../docs/kugetsu-setup.md) for full remote access setup including host-side port forwarding and firewall configuration.
|
||||
|
||||
## Without kugetsu
|
||||
|
||||
If kugetsu is not available, use opencode directly:
|
||||
|
||||
Reference in New Issue
Block a user