====== Member BBSes ======

Every BBS that connects to your hub has an account: a **system tag**, an SSH user name and a password.

===== Adding a BBS =====

<code>
doorhub bbs add <TAG> "<BBS name>" [--user <ssh user>] [--contact "<text>"]
</code>

^ Part ^ Meaning ^
| ''TAG'' | 2 to 8 letters or digits, shown in front of the BBS's players' names (''[EXB]Name''). Must be unique. |
| ''--user'' | The SSH user name for the BBS. Default: the tag in lower case followed by ''_bbs''. Lower case letters, digits, ''_'' ''.'' and ''-''. |
| ''--contact'' | Anything that helps you reach the sysop: email, netmail address. |

The command prints a complete ''doorhub-connector.ini'' with a new random 32-character password:

<code>
$ doorhub bbs add EXB "The Example BBS" --contact "sysop@example.com"
Added EXB (The Example BBS). The password is shown only now.

; doorhub-connector.ini for The Example BBS
system_tag      = EXB
ssh_username    = exb_bbs
ssh_password    = 8kQmZr2vYh...
local_interface = 127.0.0.1
local_port      = 9998
ssh_host        = hub.example.com
ssh_port        = 2022
rlogin_host     = 127.0.0.1
rlogin_port     = 513
</code>

**The password is shown only this once.** The hub keeps only a bcrypt hash of it. Save the output to a file and send it to the member sysop over a private channel (email to an address you know is theirs, netmail, an encrypted file), never in a public message base. Then point them to [[doorhub:join_a_hub|Joining a hub]].

''ssh_host'' and ''ssh_port'' come from the ''public_host'' and ''public_port'' [[doorhub:settings|settings]], so set those first.

===== Looking after members =====

^ Command ^ What it does ^
| ''doorhub bbs list'' | All members, enabled or not, and when each was last seen |
| ''doorhub bbs show <TAG>'' | Details, contact, notes and number of players |
| ''doorhub bbs passwd <TAG>'' | A new password; prints a new ini. The old password stops working for new logins. |
| ''doorhub bbs disable <TAG>'' | Block the BBS. New sessions are refused at once, even through a tunnel that's already open. Games already running carry on. |
| ''doorhub bbs enable <TAG>'' | Allow it again |
| ''doorhub bbs note <TAG> "<text>"'' | Keep a note (shown by ''bbs show'') |
| ''doorhub bbs remove <TAG>'' | Delete the account |

<code>
$ doorhub bbs list
TAG  NAME                  SSH USER          STATUS   LAST SEEN
KAL  Kalgoorlie Retro BBS  kalgoorlie_retro  enabled  2026-11-09 11:32
EXB  The Example BBS       exb_bbs           enabled  never
</code>

**Last seen** is the last time the BBS's connector logged in. A connector keeps one SSH connection open and shares it between callers, so this changes when the connector starts or reconnects, not for every game. To see who is playing, use the [[doorhub:logs_and_backups|log]] or ''doorhub player list''.

**Removing a BBS** keeps its players in ''players.json'' and on your Synchronet, so their game progress isn't lost if the BBS comes back with the same tag. To remove the players too, delete the ''Name (TAG)'' users in your Synchronet user editor and their entries in ''players.json''.

**A lost password:** use ''bbs passwd'' and send the new ini. There's no way to read an old password back.

**A BBS changing its tag:** add a new account with the new tag. Players are tied to their tag, so they start fresh in the games under the new one.