Skip to main content

viclix

Official Viclix CLI — deploy and manage your Viclix projects from the terminal.

Install

pip install viclix

This exposes a viclix command on your PATH.

Quick start

# 1. Log in once with an account API token (Dashboard → Settings → Tokens)
viclix login

# 2. Inside your project's git repo, register + deploy it
cd my-app
viclix init

# 3. Ship changes anytime
viclix deploy

viclix login stores your token in ~/.viclix/config.json. Set VICLIX_HOME to change that location.

How init picks your repo

  • If the repo already has an origin remote, viclix init registers that repo and branch with Viclix — no GitHub token needed.
  • If there's no remote yet, it offers to create a private GitHub repository and push your code (this path needs a GitHub token: pass --github-token, store one with viclix login --github-token ..., or paste it when prompted).

What the GitHub token needs

Classic token — tick the repo scope. That's the whole setup.

Fine-grained token (github_pat_…) — choosing "All repositories" is not a permission grant, so set all of these:

Setting Value
Resource owner your account (or the org that will own the repo)
Repository access All repositories — "Only select" can't create repos
Administration Read and write — required to create repos
Contents Read and write
Metadata Read-only (selected automatically)

Without Administration: Read and write, GitHub answers repo creation with 403 Resource not accessible by personal access token. You can add the permission to an existing token at https://github.com/settings/personal-access-tokens — no need to regenerate it.

Commands

Command What it does
viclix login Save your account token (--token, --base-url, --github-token).
viclix logout Remove stored credentials.
viclix whoami Show which account/endpoint you're logged into.
viclix init Register the current repo as a Viclix project and deploy it.
viclix deploy Commit, push and trigger a rebuild (--full for a full rebuild).
viclix hotfix Push and fast-sync the container (-i reinstall deps, -nr no restart).
viclix status / viclix info Inspect the project.
viclix logs-build / viclix logs-app Tail build / app logs.
viclix restart / viclix sleep / viclix start Lifecycle controls.
viclix exec --cmd "..." Run a command inside the container.
viclix pip-install [--packages "a b"] Install packages in the container.

Databases, env vars & static files

init and deploy accept the same setup the dashboard wizard offers:

# SQLite (file lives in your repo, referenced by path)
viclix init --db sqlite --sqlite-path ./data/app.db

# SQLite seeded from a local file uploaded out-of-band (large / git-ignored .db)
viclix init --sqlite-file ./local/app.db          # implies --db upload

# Managed Postgres (credentials injected as DATABASE_URL)
viclix init --db shared        # or: --db dedicated

# Environment variables (file and/or inline, repeatable)
viclix init --env-file .env --env DEBUG=false --env TZ=UTC

# Cached static path
viclix init --static /static/ --cache-max-age 86400

The same flags work on an existing project — viclix deploy --env-file .env, --static /assets/, or --sqlite-file seed.db applies the change, then pushes and rebuilds so the next build picks it up. --env merges with existing keys.

Flag Applies to Meaning
--db none|sqlite|upload|shared|dedicated init Database mode.
--sqlite-path PATH init, deploy Where the .db lives / is written (default ./data/app.db).
--sqlite-file FILE init, deploy Upload a local .db out-of-band.
--env-file FILE init, deploy Load a .env.
--env KEY=VALUE init, deploy Set one var (repeatable).
--static PREFIX init, deploy Edge-cached static path (e.g. /static/).
--cache-max-age SECONDS init, deploy Cache duration for the static path.

Per-project state (its API key) is saved to a .viclix file in the repo, which is git-ignored by default.

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

viclix-0.1.25.tar.gz (57.2 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

viclix-0.1.25-py3-none-any.whl (64.7 kB view details)

Uploaded Python 3

File details

Details for the file viclix-0.1.25.tar.gz.

File metadata

  • Download URL: viclix-0.1.25.tar.gz
  • Upload date:
  • Size: 57.2 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.10.6

File hashes

Hashes for viclix-0.1.25.tar.gz
Algorithm Hash digest
SHA256 4eb29d04b4e709a08948f48c9312f9d5cf102293e3bfa91ecbe071bc6f74d41e
MD5 912a08eaf9fe9c2aab0e30c9623ee2c2
BLAKE2b-256 051246945fdbc5ad8742900f1bb9e987829ff00eeba90272583b3371da41b44c

See more details on using hashes here.

File details

Details for the file viclix-0.1.25-py3-none-any.whl.

File metadata

  • Download URL: viclix-0.1.25-py3-none-any.whl
  • Upload date:
  • Size: 64.7 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.10.6

File hashes

Hashes for viclix-0.1.25-py3-none-any.whl
Algorithm Hash digest
SHA256 74036f60d03339fec92a0a984159267524426a22e8a5d7c741aa45fa98f66ea2
MD5 0fb84edb919e620adcd03ef94e1f9e51
BLAKE2b-256 7625d1f2685766cf6b6464552476804a3ae5e238be67240aa4802515df889986

See more details on using hashes here.

Release history Release notifications | RSS feed

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page