Copy config template:
```
cp config/.env.example config/.env
```

Fill in config/.env with actual values

Key-based authentication:

SSH_HOST=your-server.example.com
SSH_USER=ubuntu
SSH_AUTH_METHOD=key
SSH_KEY_PATH=/absolute/path/to/private/key
SSH_KEY_PASSWORD=
SERVER_PROJECT_PATH=/path/to/project

Password-based authentication:

SSH_HOST=your-server.example.com
SSH_USER=ubuntu
SSH_AUTH_METHOD=password
SSH_PASSWORD='your account password'
SERVER_PROJECT_PATH=/path/to/project

Make script executable:
```
chmod +x scripts/connect.sh
```

For Cloud Runtime

Set environment variables in your cloud configuration:

SSH_HOST — server hostname or IP
SSH_USER — SSH username
SSH_PORT — SSH port (optional)
SSH_AUTH_METHOD — auto, key, or password (optional, defaults to auto)
SSH_KEY_PATH — path to private key for key authentication
SSH_KEY_PASSWORD — key passphrase (optional)
SSH_PASSWORD — SSH account password for password authentication
SERVER_PROJECT_PATH — project directory on server

For password authentication, the local runtime must have either sshpass or expect. If the host key is not trusted yet, connect once manually or add the host to known_hosts before running non-interactive commands.

Important Notes

Git operations: Do NOT run git pull on the server. User will handle git sync manually.
Code location: Code is in a private repo, changes must be pushed first then pulled by user.
Docker: Use docker compose (not docker-compose) on the server.

Example Commands

# View logs
scripts/connect.sh "docker compose logs backend --tail 100"

# Restart service
scripts/connect.sh "docker compose restart backend"

# Rebuild and restart
scripts/connect.sh "docker compose build backend && docker compose up -d backend"

# Check status
scripts/connect.sh "docker compose ps"

ssh-remote-connection

SSH Remote Connection

Usage

Setup

For Claude Code (local)