# Connection reference

- SSH gateway: `root@124.243.245.42`
- HighGo client: `/opt/HighGo4.5.7-see/bin/psql`
- Database endpoint: `39.98.44.136:6023`
- Database: `highgo`
- User: `sysdba`
- Default schemas: `shz,public`
- Detected server: HighGo Security Enterprise Edition Database System 4.5.10
- Password source: `../.password`, mode `600`; override with `HIGHGO_PASSWORD_FILE`

## Test environment

- SSH gateway: `root@47.111.103.66:22`
- HighGo client: `/opt/HighGo4.5.7-see/bin/psql`
- Database endpoint from the test profile: `127.0.0.1:5866` (on the test server)
- Database: `highgo`
- User: `sysdba`
- Default schemas: `shz,public`
- Password source: `HIGHGO_TEST_PASSWORD_FILE` when set; otherwise the existing `HIGHGO_PASSWORD_FILE` or `../.password`

The test connection is made by SSHing to `47.111.103.66` and running the HighGo client there against its loopback database endpoint. Override the test endpoint with `HIGHGO_TEST_SSH_HOST`, `HIGHGO_TEST_SSH_PORT`, `HIGHGO_TEST_PSQL_PATH`, `HIGHGO_TEST_DB_HOST`, `HIGHGO_TEST_DB_PORT`, `HIGHGO_TEST_DB_NAME`, or `HIGHGO_TEST_DB_USER` if the server layout differs.

The SSH gateway must be reachable with the workstation's existing SSH key. Keep credentials out of commands, logs, responses, and `SKILL.md`.