Kimura SCM

Appearance

Standalone File Server ​

Overview ​

Use the Standalone File Server tab in Visual Server to host a File server that connects to an existing Kimura server.

In this mode, you configure the server endpoint to connect to and the standalone file server settings used to register and run that file server instance.

A standalone file server authenticates with the Kimura server as a regular user, so it must provide user credentials (name and password).

When you use it ​

Use this mode when file serving is hosted separately from the central Kimura server, for example to isolate storage traffic or deploy dedicated file server nodes.

What you can do here ​

  • Configure the Kimura server endpoint the standalone file server connects to
  • Configure standalone file server settings (name, password, hosting port, and storage path)
  • Configure certificate options (client certificate and server certificate requirement)
  • Start and stop standalone file server hosting
  • Monitor connection status and sync status from the status area at the bottom of the tab
  • Configure endpoint bindings to other file servers when the standalone file server is connected
  • Validate service status for operational readiness and troubleshooting

Typical flow ​

  1. Open Visual Server and select Standalone File Server.
  2. Enter or confirm the server endpoint and file server settings (name, password, port, and storage path).
  3. Optionally configure certificate options (client certificate and server certificate requirement).
  4. Start the file server and monitor Status and Sync status at the bottom of the tab.
  5. When connected, use Setup bindings to other file servers if needed.

Notes ​

  • By default, the server endpoint is localhost:8666.
  • By default, the standalone file server path points to the local AppData KimuraSCM FileServers folder.
  • While the standalone file server is running, input fields are disabled and become editable again after stopping the file server.
  • When the file server is acting as a secondary file server, it automatically synchronizes changes from the primary file server. This is reflected in Sync status.