Skip to content

user.md

Latest commit

 

History

History
43 lines (30 loc) · 1.55 KB

user.md

File metadata and controls

43 lines (30 loc) · 1.55 KB
Raw

Launch a local Perforce server

Enable Perforce Server under Settings → Features to use these tools.

Perforce controls are offered for configured local folders. Launch and console actions require Linux and separately supplied Perforce executables/data.

Configure the folder

Place remoteConfig.ini in the local folder:

[Perforce]
p4d_path = p4d
data_path = data
port = 1666

Paths are relative to that folder. All three values are needed. An optional server.id in the data folder is shown in the launch button.

Start and use the console

  1. Select the configured local folder on Workspaces.
  2. Choose Launch P4D and inspect the new terminal.
  3. Use Open P4 Console after the server has started.

Supply an executable p4 client beside remoteConfig.ini, or put it on PATH. The console supplies the configured server address automatically. Commands such as p4 info use that server; interactive password prompts work normally.

Logistics provides no server stop controls, provisioning or health monitoring. Manage the server process from its terminal or your usual service tools.

More help

See Using Logistics for navigation and settings.

This is a local server launcher, not a Perforce changelist or workspace client. Missing controls usually mean the selected folder lacks a valid [Perforce] section; disabled launch controls on Windows/macOS reflect the Linux-only support. Server data persists at the configured data_path; closing Logistics does not provide a server stop operation.