CLI client for Vikunja
This is a simple CLI for Vikunja > The todo app to organize your life.
It provides a command line interface for adding, viewing and editing todo tasks on a Vikunja Server. The goal is to support a command line based task workflow ~ similar to taskwarrior.
Installation
- Install from pypi:
pip install vja vja --help
- Upgrade existing version:
pip install vja --upgrade
Configuration
Before using vja you must provide a configuration.
- Create a configuration file $HOME/.vjacli/vja.rc with ~ the following contents
[application] frontend_url=https://try.vikunja.io/ api_url=https://try.vikunja.io/api/v1
(If you cloned from git, you may copy the folder .vjacli to your$HOMEdirectory instead.) - Adjust to your needs.
frontend_urlandapi_urlmust point to your own Vikunja server.
Especially, the api_url must be reachable from your client. This can be verified, for example bycurl https://mydomain.com/api/v1/info
Usage
vja --help
vja ls
(You will be prompted for your account on first usage and any time the access token expires.)
More documentation is available on Features.md
Development
Prepare python virtual environment
Python >= 3.8 is recommended. First create a local environment:
pip install virtualenv
virtualenv venv
source venv/bin/activate
Local build
Build, install and perform some integration-test. For integration test, a real Vikunja instance is launched locally via docker-compose. Local development install:
pip install -r requirements_dev.txt
pip install -e .
Alternatively: full local installation:
# pip uninstall -y vja;rm -rf build dist vja.egg-info; python setup.py sdist bdist_wheel; pip install dist/*.whl;
Run integration test (requires docker and docker-compose)
docker-compose -f tests/docker-compose.yml up -d
./run.sh
VJA_CONFIGDIR=tests/.vjatest pytest
docker-compose -f tests/docker-compose.yml down
Metadata
Release files for vja 1.2.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 | Provenance | Actions |
|---|---|---|---|---|
| vja-1.2.0.tar.gz | 19.5 kB | Without provenance | Details for vja-1.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| vja-1.2.0-py3-none-any.whl | Python 3 | none | any | Details for vja-1.2.0-py3-none-any.whl |
Total release size: 54.7 kB
Release files / vja-1.2.0.tar.gz
| Download URL | vja-1.2.0.tar.gz |
|---|---|
| Size | 19.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f1a0b55e2e5c6145bb9d521ebe182de30f44e8dfdfe3a776d679bbf2129276f5
|
|
BLAKE2b-256 checksum How to use checksums |
5db65098855e70a4021067fd69ddf2090973134ee7e1f98dece8ed033289513f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.2
|
Release files / vja-1.2.0-py3-none-any.whl
| Download URL | vja-1.2.0-py3-none-any.whl |
|---|---|
| Size | 35.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8c6363c2ce823bc80a229fc44e61ec2ea055223072c30ef7d1e9992a82b2c5ba
|
|
BLAKE2b-256 checksum How to use checksums |
dc7413480964c8da299f08fe8665d5a36b922194d0b1c62149a2e17ba384662b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.2
|
Security for vja 1.2.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.