There is no need to configure ButConnect at all. It can be controlled completely interactive or from the command line.
But the real power of using ButConnect comes with the list of configured connections which is growing over time and thereby builds a pool of ready-to-use configuration entries for your targets.
When creating those configuration entries, ButConnect's ‘CONF’ mode is of great help:
Whenever you need to access a new target, use the ‘CONF’ mode to create the appropriate connection in the configuration file. It's then ready to be used from there and it's available for later use, too. That way, you accumulate (and also document and organize) the important connection settings.
Those configuration sections may cover completely different ways of accessing the remote hosts you need
to support regularly:
Some use your client's SSH server, some don't. Some apply to unattended hosts, others don't. Some use VNC, others RDP. Or a command line. Some work with any browser, others require a specific one. Like Firefox. Or Chromium. Some even still need Internet Explorer. Some use proxy settings, others don't. Different servers, users, keys, ... you get it.
But all of those pre-configured connections can be started just by choosing their name and entering a passphrase (if necessary). Everything else is handled by ButConnect.
Here are some snippets:
(This is the one from the configuration page, actually. Stay tuned — real, commented snippets are coming soon.)
port = 443
mode = target
dest = postgres.example.org
loop = 5432
# The configuration to access that
# postgres endpoint could be ...
; mode = source
; orig = 127.0.0.1
; hook = 5432
local = 80
# The remote side could be ...
; remote = 8080