Skip to main content

fmu-settings-cli

ci

fmu-settings-cli is the CLI package for fmu-settings.

Usage

To launch the application simply run

fmu settings

The command starts one server for both the API and the built GUI on port 8000, and opens the FMU Settings home page in your web browser.

GUI development

To develop the GUI, start only the API. You can also use --reload if you change API code.

fmu settings api

By default the API will set CORS rules restricting requests to a default host and port (localhost:8000). In development with a GUI it's likely your frontend port will be something different. You can specify this like so:

fmu settings api --gui-port 5173

This will update the CORS rules in the API to accept requests from localhost:5173.

The API authorizes all requests with a randomly generated token. When starting the API for use in development this token can be printed by setting the FMU_SETTINGS_PRINT_TOKEN environment variable or providing the --print-token flag.

fmu settings api --gui-port 5173 --print-token
# or
export FMU_SETTINGS_PRINT_TOKEN=true
# or
FMU_SETTINGS_PRINT_TOKEN=true fmu-settings api --gui-port 5173

It's also possible to print the full URL a user would be directed to with a similar URL flag and environment variable.

fmu settings api --gui-port 5173 --print-url
# or
export FMU_SETTINGS_PRINT_URL=true
# or
FMU_SETTINGS_PRINT_URL=true fmu-settings api --gui-port 5173

Note that these additional flags are intended for development so they only work with fmu settings api subcommand.

CLI development

Clone and install into a virtual environment.

git clone git@github.com:equinor/fmu-settings-cli.git
cd fmu-settings-cli
# Create or source virtual/Komodo env
pip install -U pip
pip install -e ".[dev]"
# Make a feature branch for your changes
git checkout -b some-feature-branch

Run the tests with

pytest -n auto tests

Ensure your changes will pass the various linters before making a pull request. It is expected that all code will be typed and validated with mypy.

ruff check
ruff format --check
mypy src tests

See the contributing document for more.

Metadata

Release files for fmu-settings-cli 1.3.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for fmu-settings-cli 1.3.0
File Size Uploaded
fmu_settings_cli-1.3.0.tar.gz 189.6 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for fmu-settings-cli 1.3.0
File Interpreter ABI Platform
fmu_settings_cli-1.3.0-py3-none-any.whl Python 3 none any Details

Total release size: 226.8 kB

Release files / fmu_settings_cli-1.3.0.tar.gz

Download URL fmu_settings_cli-1.3.0.tar.gz
Size 189.6 kB
Tags Source
SHA-256 checksum
How to use checksums
99b4a489fe4823e91617be1bc0542d174266009540c717f620561735afcedec8
BLAKE2b-256 checksum
How to use checksums
8c53f37174b3c47e3ae19b51fcea8d7fe4934f1d707775adff700d6d073944d6
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 16, 2026.

Transparency log

Release files / fmu_settings_cli-1.3.0-py3-none-any.whl

Download URL fmu_settings_cli-1.3.0-py3-none-any.whl
Size 37.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
d94da68dad9474bfe3bdef5fb50526273248a86c63ba205fbd5a53328b615d4d
BLAKE2b-256 checksum
How to use checksums
c1a9be60a20173445116f9d4e4c06ddc3dc0c931d9540f3c9c4264ae5c95560f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 16, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

1.3.0 This release

2 release files

1.2.0

2 release files

1.1.1

2 release files

1.1.0

2 release files

1.0.0

2 release files

0.1.1

2 release files

0.1.0

2 release files

0.0.1

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page