Skip to main content

EXE

Windows users may prefer the pre-packaged Windows delivery package for Enterprise and Designer.

Community does not ship as an EXE. For most Community installs, use Docker. Use From source (advanced) only if you need a local source checkout for development or contributor work.

Enterprise and Designer​

Prerequisites​

  • Windows machine
  • One Outburn-delivered Windows package for Enterprise and Designer
  • A valid Enterprise license file (*.lic)

Run​

Use one shared folder for the Windows install so the server, Designer, .env, and license file all stay together.

  1. Place the files from the Outburn-delivered Windows package in a single folder.
  2. Put your Enterprise license file (*.lic) in that same folder. One .lic file can be used by both the server and Designer.
  3. Configure runtime settings:
    • For a simple folder-local setup, create or edit .env in that same folder.
    • If you already manage settings at the machine or service level, set the same values as Windows environment variables instead.
  4. Run fume-server.exe from that folder.
  5. If you want the browser UI, run fume-designer.exe from that same folder.
  6. Open the server and Designer in your browser.

Starter .env example:

# Use .env when you want the Windows package to carry its settings with it.
# If you already manage Windows environment variables centrally, set the same values there instead.

FUME_SERVER_URL=http://localhost:42420

# Optional: only set this if you want a non-default Designer port.
# FUME_DESIGNER_PORT=3000

# Optional: only set this if you want a non-default server port.
# SERVER_PORT=42420

Shared configuration​

  • The same .env file or Windows environment variables can coordinate both the server and Designer.
  • The same .lic file can be used by both applications when it is placed in the working folder.
  • FUME_SERVER_URL must match the address the browser can actually reach.
  • If the browser will connect from another machine, do not leave FUME_SERVER_URL on localhost.

What success looks like​

  • The server responds on http://localhost:42420 by default.
  • The Designer opens on http://localhost:3000 by default.
  • Designer uses the same server address that you configured in .env or in Windows environment variables.

Configure​

Logs​

  • Console output from both applications while they are running
  • Server log files under ./logs/ relative to the working directory