Skip to content

GUI: AcqStore Server

Open the left toolbar and click AcqStore Server (network node icon) to control a local HTTP server for external browser or JavaScript clients.

This panel is optional. CloudScope’s main job remains loading, visualizing, and analyzing acquisitions. The server is a side service you can start when other thin clients need HTTP access to AcqStore on this machine.

What it does

  • Starts and stops the local AcqStore Server process (default http://127.0.0.1:8767).
  • Lets you check status, see who is using the server port, and free a busy port.
  • Opens the built-in demo and interactive API docs in your browser when the server is running.

What it does not do

CloudScope does not load images, run analysis, or fetch planes through this HTTP API. Those workflows stay in-process via AcqStore. External clients that connect to the server are independent of whatever files you have open in CloudScope.

Typical use

  1. Open AcqStore Server on the left toolbar.
  2. Click Start server.
  3. Use Open demo or API docs if you want a browser client, or point your own HTML/JS client at the server URL.
  4. Click Stop server when finished (or quit CloudScope — a server started from this process is stopped on quit).

If the port is busy, use Who uses server port? and Free server port, then Start server again. Use Check status to refresh the status line (the panel does not poll in the background).

Start with CloudScope (optional)

In Config, you can enable Start AcqStore Server with CloudScope. It is off by default. When on, CloudScope tries to start the server during launch; a busy port or start failure is reported in the Server panel and never blocks CloudScope from opening. See App config.

See also