Bashpack is a versatile and user-friendly command-line script manager. It is designed to use scripts as regular commands on any Linux distro. It simplifies script management, security, and automation, making your administrative tasks more efficient.
It can be compared to PyPI for Python, PowerShell Gallery for PowerShell, Registry for Docker, Go Packages for Go etc..., but for Shell scripts made to be compatible with any Unix based OS.
Anyone can self-host its own subcommands repositories, and even its own CLI repository.
- Script Management: Easily install, update, and remove scripts as subcommands.
- Automation: Automate routine tasks to save time and reduce human error.
- Security: Enhance the security of your Linux systems with minimal effort.
- User-Friendly: Accessible to both novice and experienced users.
To manage your Bashpack installation, copy/paste the following command blocks into your Linux terminal.
curl -sL https://raw.githubusercontent.com/bashpack-project/bashpack/main/bashpack.sh -o bashpack.sh \
&& chmod +x bashpack.sh \
&& sudo ./bashpack.sh -i \
&& rm bashpack.shsudo bp -usudo bp --self-deletebp --helpInstall a subcommand from the repositories
sudo bp --get <subcommand>Remove a subcommand
sudo bp --delete <subcommand>List available remotes and installed subcommands
sudo bp --listA configuration file is located at /etc/bashpack/bashpack.conf. It is created and maintained automatically, and you can customize it according to your needs.
Logs are maintained in /var/log/bashpack. You can quickly view the logs using the following command:
sudo bp --logs- POSIX Compatibility: Bashpack is POSIX-compliant, meaning it can be installed on any POSIX system. It was first written in Bash, but is now written in Bourne shell. That being said, every specific distro software support needs to be added one by one in the subcommands.
- Root Access: Root/sudo access is required for installation and most operations.
- Automatic Updates: Bashpack can automatically update itself.
- Repositories: Multiple repositories exist; for production usage, only the main one should be used.
This project is licensed under the MIT License. See the LICENSE file for details.