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.
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 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
1 maintainer
Release files for arcsecond 4.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| arcsecond-4.0.0.tar.gz | 731.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| arcsecond-4.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 873.8 kB
Release files / arcsecond-4.0.0.tar.gz
| Download URL | arcsecond-4.0.0.tar.gz |
|---|---|
| Size | 731.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e2123454d35b0876866b1c986851361af0425c43b5564fa55b72fd449460804f
|
|
BLAKE2b-256 checksum How to use checksums |
e576d705d574fbbf6b9d8f9cfaf9ed8076f367271f9cf8f11169a439448c503e
|
| 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 Sep 22, 2026.
Transparency logRelease files / arcsecond-4.0.0-py3-none-any.whl
| Download URL | arcsecond-4.0.0-py3-none-any.whl |
|---|---|
| Size | 142.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
118b82619a1e170de640c3a96b90a78924bf9d7e71c74938cc752d93a1c5facb
|
|
BLAKE2b-256 checksum How to use checksums |
534e393dfa5d8bb7d1ab0889a20ecc6050f6cb4c4e7ec43d14d3fa454a427bf2
|
| 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 Sep 22, 2026.
Transparency log
