Create and check your first board

For the current D1–D3 source at schema 37, follow the Quick Start to build SPITFIRE NG and run interactive setup. Setup makes a new board; it does not migrate a classic DOS board or install a background service.

If you downloaded the older 0.1.0 Apple Silicon archive, use its package-specific instructions. Do not assume that the older binary has current-source features.

Choose a safe first configuration

Use a new directory, a unique Sysop login and password, your board's timezone, and only the personal-profile fields you need. Keep the initial listener bound to 127.0.0.1, which is your own computer. Two caller nodes let you test simultaneous calls with separate accounts.

A node in this screen is a caller slot. A CircuitNET Node ID is a different thing: a short assigned identifier for a BBS in the network.

Know what belongs to your board

  • spitfire.toml contains the board configuration.
  • system/ holds menus, installed presentation packages and other managed resources.
  • display/ holds your board-owned display overrides.
  • work/ includes the native database as well as working state; do not treat the whole directory as disposable cache.
  • message/ and external/ are part of the configured board layout.

Keep customization in the board-owned display layer. Custom display screens explains installed packages versus your own overrides.

Administer without losing changes

The configuration guide explains the stopped-board menu and current sfconfig application. Static settings require Save; conference and file-area edits in the compatibility menu take effect immediately. Stop the board and other offline tools when a procedure requires exclusive access.

Use the Sysop guide for routine operation and the caller policy guide for registration, time limits and access. Broader configuration/operations acceptance remains future D5 work; this does not erase the operator tools already available.

Make two real test calls

  1. Start the board and log in as the setup-created Sysop.
  2. Post a welcome message in a starter conference; new boards do not invent a conversation for you.
  3. Register an ordinary test caller, then read and reply to the welcome post.
  4. Check conference selection, new-message scans, next/previous, menu return and Goodbye.
  5. Confirm a reconnect keeps that caller's read position, and that ordinary callers cannot enter restricted areas.

Different accounts may use separate nodes concurrently. A duplicate login to the same account must not disturb its existing session. Actual accepted caller/message tests used Apple Silicon Telnet; this page is guidance, not a claim that this website pass reran BBS acceptance.

Finish with recovery practice

Log off, stop the board and make a cold backup. Rehearse a new-root restore before depending on it. Updates and runtime rollback explains the later managed-installation path; storage planning explains which files need separate protection.

Full Files caller UX/transfers, Doors, installers/services, classic migration and final public-preview hardening remain in development. CircuitNET applications remain closed.

Source: editorial sequence based on the public operator guide, configuration and accepted D1–D3 evidence. Older source-guide limitations are reconciled with the current operator and package contracts.