tardyon
If you write custom scripts, tardyon helps you maintain and invoke them.
Usage
Example script
Save the following script as $HOME/.local/bin/tardy/all/upgrade.all
#!/bin/sh
# Escalate session once
sudo -v || exit 1
# Update and upgrade APT packages
sudo apt update && sudo apt upgrade -y
# Update Flatpak packages
flatpak update -y
You can now call tardyon upgrade all to upgrade packages across all your package managers
(in this example, APT and Flatpak).
Organizing scripts
Tardyon follows a strict but simple organizing principle: tardyon foo bar will invoke the script
$HOME/.local/bin/tardy/bar/foo.bar
Commands are shaped like ordinary English clauses, an imperative with a vocative.
So you write tardyon clear cache rather than tardyon cache clear.
Scripts can be any executable file with a shebang, or even a compiled binary.
Special commands
tardyon show yourself: Opens the folder containing your scripts.tardyon check yourself: Validates script names, detects duplicates, and fixes execution permissions.
Development environment
Initialize with uv sync. Test with uv run pytest.
Release
git tag -a 2.0.0 -m "Version 2.0.0"
uv build
uv publish # uses tag for version number
Sharing and contributions
tardyon
https://lofidevops.neocities.org
Copyright 2023 David Seaward and contributors
SPDX-License-Identifier: AGPL-3.0-or-later
Shared under AGPL-3.0-or-later. We adhere to the Contributor Covenant 2.1, and certify origin per DCO 1.1 with a signed-off-by line. Contributions under the same terms are welcome.
Submit security and conduct issues as private tickets. Sign commits with
git commit --signoff. For a software bill of materials run reuse spdx.
Colophon
Originally inspired by Ansible but with subluminal ambition.
Metadata
Release files for tardyon 5.0.3
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 |
|---|---|---|---|---|
| tardyon-5.0.3.tar.gz | 63.0 kB | Without provenance | Details for tardyon-5.0.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tardyon-5.0.3-py3-none-any.whl | Python 3 | none | any | Details for tardyon-5.0.3-py3-none-any.whl |
Total release size: 67.2 kB
Release files / tardyon-5.0.3.tar.gz
| Download URL | tardyon-5.0.3.tar.gz |
|---|---|
| Size | 63.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dd0dc9d23de3d76e69751f8093b2326266e6adf4edd89b3b481288824b68ae07
|
|
BLAKE2b-256 checksum How to use checksums |
5b1413e7967f19f3885baa8ce891a4c1d58bcc56312a102ed1a0a3376ec1f3dd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.20 {"installer":{"name":"uv","version":"0.11.20","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / tardyon-5.0.3-py3-none-any.whl
| Download URL | tardyon-5.0.3-py3-none-any.whl |
|---|---|
| Size | 4.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ffded833dcb693c74d810eb4c1303e5ddd6d6444d4b34d537c90056be2a643b5
|
|
BLAKE2b-256 checksum How to use checksums |
50672803df3a292132270b8a35eb5f9bf1c067b1ef366a0e07e565b1c3f999ff
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.20 {"installer":{"name":"uv","version":"0.11.20","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for tardyon 5.0.3
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.