Arcsecond CLI

The Command-line interface (CLI) for Arcsecond. It can be used as Python module too. The CLI makes it easy to login/register and access Arcsecond resources, public and private ones.

Read the docs

Running Arcsecond.local

The CLI owns the whole lifecycle of a self-hosted installation; there is no docker command to type:

$ arcsecond setup --lan-host 192.168.1.42   # writes .env and docker-compose.yml
$ arcsecond token set                       # the access token Arcsecond gave you, once per machine (setup asks too)
$ arcsecond start                           # first run downloads the images
$ arcsecond status
$ arcsecond logs backend -f
$ arcsecond restart backend worker          # after editing .env
$ arcsecond update                          # newer images, refreshed compose file
$ arcsecond stop

Every one of these finds the installation in the current folder, or in the folder arcsecond setup last ran in, or where --dir points.

Which server the CLI talks to

The CLI points at one API server at a time — the cloud by default, or a server you registered, typically your own Arcsecond.local — and every command follows that pointer:

$ arcsecond api                     # list them, * marks the current one
$ arcsecond api use local           # `setup` registered `local` for you
$ arcsecond login                   # on that server

Credentials are kept per server. For a script or a cron job, ARCSECOND_API=<name> selects a server for that process alone, without moving the pointer.

Configuration

Credentials and settings live in ~/.config/arcsecond/, alongside the list of registered cameras and the live-image proxy's runtime files.

Set ARCSECOND_CONFIG_DIR to put them somewhere else:

$ ARCSECOND_CONFIG_DIR=~/.config/arcsecond-observatory arcsecond login

Useful for keeping a personal account and an observatory's apart, and for containers or CI jobs that should not touch a home directory. Child processes the CLI starts — such as the background proxy from arcsecond proxy start — inherit it.

Development

The project uses uv for environment and dependency management. After forking and cloning:

$ cd ~/arcsecond-cli
$ uv sync --extra webcam --group dev
$ uv run arcsecond --help
$ uv run pytest

uv sync creates .venv/ and installs the project with its webcam extra and the dev dependency group (pytest, black, flake8, isort). Prefix commands with uv run or activate the venv with source .venv/bin/activate.

The test suite writes nothing to your own configuration: an autouse fixture in tests/conftest.py points ARCSECOND_CONFIG_DIR at a temporary directory for the whole run. Several tests save real-looking credentials, so if you add one that touches ArcsecondConfig, leave that fixture in place.

License

Metadata

Release files for arcsecond 4.3.3

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

Source distribution (sdist)

Source distribution for arcsecond 4.3.3
File	Size	Uploaded
arcsecond-4.3.3.tar.gz	755.0 kB	Oct 4, 2026	Details

Built distribution (wheel)

Table of built distributions (wheels) for arcsecond 4.3.3
File	Interpreter	ABI	Platform	Reset
arcsecond-4.3.3-py3-none-any.whl 161.8 kB Oct 4, 2026	Python 3	none	any	Details

Total release size: 916.8 kB

Release files / arcsecond-4.3.3.tar.gz

Download URL	arcsecond-4.3.3.tar.gz
Size	755.0 kB
Tags	Source
SHA-256 checksum How to use checksums	`c7101ccf0710c5de65e81bc17f15d36d3552d6c9a2b6f4876f229fb7d3fa196b`
BLAKE2b-256 checksum How to use checksums	`9c316a193b6991876c5fb978b9b016841f9b73f5b50156b5bdcdf2ce0f9ce67b`
Upload date	Oct 4, 2026
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.

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/arcsecond-io/cli
Publishing commit: github.com/arcsecond-io/cli/tree/ec8f0182e9cfb9e719d04b46873f884c047aaaed

Workflow

Publishing configuration: github.com/arcsecond-io/cli/blob/ec8f0182e9cfb9e719d04b46873f884c047aaaed/.github/workflows/pythonpublish.yml
Publishing logs: github.com/arcsecond-io/cli/actions/runs/37191969897/attempts/1

Artifact

Subject: arcsecond-4.3.3.tar.gz
SHA-256 checksum: c7101ccf0710c5de65e81bc17f15d36d3552d6c9a2b6f4876f229fb7d3fa196b Verifying attestations

Release files / arcsecond-4.3.3-py3-none-any.whl

Download URL	arcsecond-4.3.3-py3-none-any.whl
Size	161.8 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`eab3d65da43dae5198454300d08f7149474c2c922921c679cf67739d53f081b7`
BLAKE2b-256 checksum How to use checksums	`1004f95303d319d8144788eea4a249ec0f73769ed64a174583a4f8f60e50a572`
Upload date	Oct 4, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.14`

Provenance

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/arcsecond-io/cli
Publishing commit: github.com/arcsecond-io/cli/tree/ec8f0182e9cfb9e719d04b46873f884c047aaaed

Workflow

Publishing configuration: github.com/arcsecond-io/cli/blob/ec8f0182e9cfb9e719d04b46873f884c047aaaed/.github/workflows/pythonpublish.yml
Publishing logs: github.com/arcsecond-io/cli/actions/runs/37191969897/attempts/1

Artifact

Subject: arcsecond-4.3.3-py3-none-any.whl
SHA-256 checksum: eab3d65da43dae5198454300d08f7149474c2c922921c679cf67739d53f081b7 Verifying attestations