Crates.io | devscripts |
lib.rs | devscripts |
version | 0.1.0-alpha.2 |
source | src |
created_at | 2024-10-04 14:12:06.090612 |
updated_at | 2024-10-04 14:12:06.090612 |
description | Run path-specific (shell) scripts without the need to modify `PATH`. |
homepage | |
repository | https://github.com/einfachIrgendwer0815/devscripts |
max_upload_size | |
id | 1396624 |
size | 54,620 |
Devscripts is a linux command-line tool that makes it easy to run (shell) scripts
depending on the user or current working directory without ever having to
modify PATH
. For more information, see How to use.
Devscripts can be installed via cargo install
, the installed executable will
be called dev
:
Latest stable version:
cargo install devscripts
Latest development version:
cargo install --git https://github.com/einfachIrgendwer0815/devscripts
The installed executable is called dev
:
dev --version
# devscripts <version>
dev --help
# <devscripts help page>
To add a script that can be run via devscripts
, follow these two steps:
[!NOTE] These scripts do not have to be shell scripts. They could also be written in, for example, python. In fact,
devscripts
will run any executable that is available in onedevscripts
paths (listed below).
Write your shell script and place it in of these locations (ascending in priority):
/usr/share/devscripts
(system-wide scripts)/usr/local/share/devscripts
(system-wide scripts)~/.local/share/devscripts
(user-specific scripts)<repo-root>/.devscripts"
(repository-local scripts, <repo-root>
is the root of a git worktree)Scripts with same names in higher-priority directories will override those in
lower-priority directories.
Additionally, devscripts
ignores file endings, so avoid having multiple
scripts with the same name in the same directory. In such a case, devscripts
will use the script it encounters first. However, there are no guarantees which
one that will be.
[!NOTE] System-wide, user-wide and repository-local script directories are configurable. See Configuration for more information.
Set the executable bit using chmod
:
chmod +x /path/to/your/script
To run any script in one of devscripts
directories, run:
dev run <SCRIPT-NAME>
# say, there is a script at ~/.local/share/devscripts/hello-world
dev run hello-world
# will run that script
If you run dev
anywhere inside a git worktree, the above mentioned
repository-local script directory will be searched for scripts as well. These
repository-local scripts do not need to be known by git.
Devscripts can be configured by creating/editing the following files (ascending in priority):
/etc/devscripts/config.toml
(global/system-wide configuration)~/.config/devscripts/config.toml
(user configuration)<repo-root>/.devscripts/.config.toml
(repository-local configuration)Higher-priority configurations will override lower-priority ones.
The current default configuration looks like this:
[paths.scripts]
# Directories for system-wide scripts.
system = [
"/usr/share/devscripts",
"/usr/local/share/devscripts",
]
# Directories for user-specific scripts.
user = [
"~/.local/share/devscripts",
]
# Directories for repository-local scripts. These paths
# are applied relative to a repository root.
repository = [
"./.devscripts"
]
Devscripts is currently in a very early stage of development, so all feature requests and PRs are very much appreciated.
This project uses the Conventional Commits standard for commit messages with the following additional rules:
!
over BREAKING CHANGE:
build
: Changes that affect the build system or dependenciesci
: Changes to CI configurationdocs
: Documentation only changesfeat
: New features or feature enhancementsfix
: Bug fixesrefactor
: Changes that do not add a feature or fix a bugperf
: Changes that improve performancestyle
: Changes that keep the meaning of the code as-is (white-space changes, formatting, etc.)test
: Adding/changing testschore
: repository-related stuff, version bumps, etc.[!NOTE] If you don't know how to use Conventional Commits, don't worry. Just write your commit messages how you always do.
Copyright 2024 einfachIrgendwer0815 and contributors.
Copyrights in this project are retained by contributors. No copyright assignment is required to contribute to this project.
Except as otherwise noted (below and/or in individual files), this project is licensed under either the Apache License, Version 2.0 (LICENSE-APACHE), or the MIT license (LICENSE-MIT), at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.