Announcement: This documentation is still in progress.
Contributing Guide
\n\n# Contributing Guidelines for Linutil
Thank you for considering contributing to Linutil! We appreciate your effort in helping improve this project. To ensure that your contributions align with the goals and quality standards of Linutil, please follow these guidelines:
Have a clear reason: Don’t change the way things are done without a valid reason. If you propose an alteration, be prepared to explain why it’s necessary and how it improves the project.
Respect existing conventions: Changes should align with the existing code style, design patterns, and overall project philosophy. If you want to introduce a new way of doing things, justify it clearly.
Check merged PRs: Reviewing merged pull requests can give you an idea of what kind of contributions are accepted and how they are implemented.
Study rejected PRs: This is especially important as it helps you avoid making similar mistakes or proposing changes that have already been considered and declined.
Be descriptive: Your commit messages should clearly describe what the change does and why it was made.
Use the imperative mood: For example, "Add feature X" or "Fix bug in Y", rather than "Added feature X" or "Fixed bug in Y".
Keep commits clean: Avoid committing a change and then immediately following it with a fix for that change. Instead, amend your commit or squash it if needed.
7. Keep Your Pull Requests (PRs) Small and Focused¶
Make small, targeted PRs: Focus on one feature or fix per pull request. This makes it easier to review and increases the likelihood of acceptance.
Avoid combining unrelated changes: PRs that tackle multiple unrelated issues are harder to review and might be rejected because of a single problem.
Review your code: Before submitting your changes, take the time to review your code for readability, efficiency and performance. Consider how your changes affect the project.
Avoid using LLMs: Don't submit AI-generated code without reviewing and testing it first. Ensure that any code you submit is thoroughly understood and meets the project's standards.
Testing Requirements: Failure to conduct testing after multiple requests may result in the closure of your Pull Request.
Expect feedback: PRs will undergo code review. Be open to feedback and willing to make adjustments as needed.
Participate in reviews: If you feel comfortable, review other contributors' PRs as well. Peer review is a great way to learn and ensure high-quality contributions.
Test the tool: Running tests and providing feedback on how the tool works in different environments is a valuable contribution.
Write well-formed issues: Clearly describe bugs or problems you encounter, providing as much detail as possible, including steps to reproduce the issue.
Propose reasonable feature requests: When suggesting new features, ensure they fit within the scope, style, and design of the project. Provide clear reasoning and use cases.
Announcement: This documentation is still in progress.
Contributing Guide
\n\n# Contributing Guidelines for Linutil
Thank you for considering contributing to Linutil! We appreciate your effort in helping improve this project. To ensure that your contributions align with the goals and quality standards of Linutil, please follow these guidelines:
Have a clear reason: Don’t change the way things are done without a valid reason. If you propose an alteration, be prepared to explain why it’s necessary and how it improves the project.
Respect existing conventions: Changes should align with the existing code style, design patterns, and overall project philosophy. If you want to introduce a new way of doing things, justify it clearly.
Check merged PRs: Reviewing merged pull requests can give you an idea of what kind of contributions are accepted and how they are implemented.
Study rejected PRs: This is especially important as it helps you avoid making similar mistakes or proposing changes that have already been considered and declined.
Be descriptive: Your commit messages should clearly describe what the change does and why it was made.
Use the imperative mood: For example, "Add feature X" or "Fix bug in Y", rather than "Added feature X" or "Fixed bug in Y".
Keep commits clean: Avoid committing a change and then immediately following it with a fix for that change. Instead, amend your commit or squash it if needed.
7. Keep Your Pull Requests (PRs) Small and Focused¶
Make small, targeted PRs: Focus on one feature or fix per pull request. This makes it easier to review and increases the likelihood of acceptance.
Avoid combining unrelated changes: PRs that tackle multiple unrelated issues are harder to review and might be rejected because of a single problem.
Review your code: Before submitting your changes, take the time to review your code for readability, efficiency and performance. Consider how your changes affect the project.
Avoid using LLMs: Don't submit AI-generated code without reviewing and testing it first. Ensure that any code you submit is thoroughly understood and meets the project's standards.
Testing Requirements: Failure to conduct testing after multiple requests may result in the closure of your Pull Request.
Expect feedback: PRs will undergo code review. Be open to feedback and willing to make adjustments as needed.
Participate in reviews: If you feel comfortable, review other contributors' PRs as well. Peer review is a great way to learn and ensure high-quality contributions.
Test the tool: Running tests and providing feedback on how the tool works in different environments is a valuable contribution.
Write well-formed issues: Clearly describe bugs or problems you encounter, providing as much detail as possible, including steps to reproduce the issue.
Propose reasonable feature requests: When suggesting new features, ensure they fit within the scope, style, and design of the project. Provide clear reasoning and use cases.
Update the documentation: If your change affects the functionality, please update the relevant documentation files to reflect this.
Automatic generation: If you decide to add functionality through a new shell script, make sure to fill out all fields in tab_data.toml and run cargo xtask docgen.
Agree to the license: By contributing to Linutil, you agree that your contributions will be licensed under the project's MIT license.
We appreciate your contributions and look forward to collaborating with you to make Linutil better!
\ No newline at end of file
diff --git a/search/search_index.json b/search/search_index.json
index d50ca280..2b5d5ee9 100644
--- a/search/search_index.json
+++ b/search/search_index.json
@@ -1 +1 @@
-{"config":{"lang":["en"],"separator":"[\\s\\-]+","pipeline":["stopWordFilter"]},"docs":[{"location":"","title":"Welcome to the LinUtil Documentation!","text":""},{"location":"#running-the-latest-release-of-linutil","title":"Running the latest release of LinUtil","text":"
To get started, run the following command in your terminal:
LinUtil is also available as a package in various repositories:
Arch Linux LinUtil can be installed on [Arch Linux](https://archlinux.org) with three different [AUR](https://aur.archlinux.org) packages: - `linutil` - Stable release compiled from source - `linutil-bin` - Stable release pre-compiled - `linutil-git` - Compiled from the last commit (not recommended) by running:
Replace `` with your preferred package. If you use [yay](https://github.com/Jguer/yay), [paru](https://github.com/Morganamilo/paru) or any other [AUR Helper](https://wiki.archlinux.org/title/AUR_helpers), it's even simpler:
paru -S linutil\n
Replace `paru` with your preferred helper and `linutil` with your preferred package. Cargo LinUtil can be installed via [Cargo](https://doc.rust-lang.org/cargo) with:
cargo install linutil\n
Note that crates installed using `cargo install` require manual updating with `cargo install --force` (update functionality is [included in LinUtil](https://christitustech.github.io/linutil/userguide/#applications-setup))
After you've ran the command, you should see a GUI on your screen; It will look something like this:
Info
LinUtil is updated weekly as of the time of writing. Consequently, features and functionalities may evolve, and the documentation may not always reflect the most current images or information.
Thank you for considering contributing to Linutil! We appreciate your effort in helping improve this project. To ensure that your contributions align with the goals and quality standards of Linutil, please follow these guidelines:
Make sure you have Rust installed on your machine. You can install it by following the instructions at rust-lang.org.
"},{"location":"contributing/#2-fork-and-clone-the-repo","title":"2. Fork and Clone the repo","text":"
Make a fork of the repo in GitHub
Clone the fork bash git clone https://github.com/YOUR_USERNAME_HERE/linutil.git cd linutil
"},{"location":"contributing/#3-make-your-changes","title":"3. Make your changes","text":"
Edit the files you want to change: Make your changes to the relevant files.
Test your changes: Run cargo run to test your modifications in a local environment and ensure everything works as expected.
"},{"location":"contributing/#4-understand-the-existing-code","title":"4. Understand the existing code","text":"
Have a clear reason: Don\u2019t change the way things are done without a valid reason. If you propose an alteration, be prepared to explain why it\u2019s necessary and how it improves the project.
Respect existing conventions: Changes should align with the existing code style, design patterns, and overall project philosophy. If you want to introduce a new way of doing things, justify it clearly.
"},{"location":"contributing/#5-learn-from-past-pull-requests-prs","title":"5. Learn from Past Pull Requests (PRs)","text":"
Check merged PRs: Reviewing merged pull requests can give you an idea of what kind of contributions are accepted and how they are implemented.
Study rejected PRs: This is especially important as it helps you avoid making similar mistakes or proposing changes that have already been considered and declined.
Be descriptive: Your commit messages should clearly describe what the change does and why it was made.
Use the imperative mood: For example, \"Add feature X\" or \"Fix bug in Y\", rather than \"Added feature X\" or \"Fixed bug in Y\".
Keep commits clean: Avoid committing a change and then immediately following it with a fix for that change. Instead, amend your commit or squash it if needed.
"},{"location":"contributing/#7-keep-your-pull-requests-prs-small-and-focused","title":"7. Keep Your Pull Requests (PRs) Small and Focused","text":"
Make small, targeted PRs: Focus on one feature or fix per pull request. This makes it easier to review and increases the likelihood of acceptance.
Avoid combining unrelated changes: PRs that tackle multiple unrelated issues are harder to review and might be rejected because of a single problem.
"},{"location":"contributing/#8-understand-and-test-the-code-you-write","title":"8. Understand and Test the Code You Write","text":"
Review your code: Before submitting your changes, take the time to review your code for readability, efficiency and performance. Consider how your changes affect the project.
Avoid using LLMs: Don't submit AI-generated code without reviewing and testing it first. Ensure that any code you submit is thoroughly understood and meets the project's standards.
Testing Requirements: Failure to conduct testing after multiple requests may result in the closure of your Pull Request.
"},{"location":"contributing/#9-code-review-and-feedback","title":"9. Code Review and Feedback","text":"
Expect feedback: PRs will undergo code review. Be open to feedback and willing to make adjustments as needed.
Participate in reviews: If you feel comfortable, review other contributors' PRs as well. Peer review is a great way to learn and ensure high-quality contributions.
"},{"location":"contributing/#10-contributing-is-more-than-just-code","title":"10. Contributing Is More Than Just Code","text":"
Test the tool: Running tests and providing feedback on how the tool works in different environments is a valuable contribution.
Write well-formed issues: Clearly describe bugs or problems you encounter, providing as much detail as possible, including steps to reproduce the issue.
Propose reasonable feature requests: When suggesting new features, ensure they fit within the scope, style, and design of the project. Provide clear reasoning and use cases.
Agree to the license: By contributing to Linutil, you agree that your contributions will be licensed under the project's MIT license.
We appreciate your contributions and look forward to collaborating with you to make Linutil better!
"},{"location":"faq/","title":"FAQ's","text":""},{"location":"faq/#how-do-i-uninstall-linutil","title":"How do I uninstall LinUtil?","text":"
You do not have to uninstall LinUtil. As it is a script you run from your terminal it only loads into your RAM. This means as soon as you close LinUtil it will be deleted off your system.
Focus on tasks that take time in Linux and automate them. (Example: Removing a user, adding a user, etc. - but mostly BASH scripts with POSIX compliance.)
Remove Binary linutil from being tracked in git and make it a github action.
Document every function and feature of linutil. (Preview panel description addition)
Create a discord server for linutil and invite the community.
Github Desktop: GitHub Desktop is a user-friendly application that simplifies the process of managing Git repositories and interacting with GitHub, providing a graphical interface for tasks like committing, branching, and syncing changes.
Neovim: Neovim is a refactor, and sometimes redactor, in the tradition of Vim. It is not a rewrite but a continuation and extension of Vim. This command configures neovim from CTT's neovim configuration. https://github.com/ChrisTitusTech/neovim
Sublime Text: Sublime Text is a fast, lightweight, and customizable text editor known for its simplicity, powerful features, and wide range of plugins for various programming languages.
VS Code: Visual Studio Code (VS Code) is a lightweight, open-source code editor with built-in support for debugging, version control, and extensions for various programming languages and frameworks.
VS Codium: VSCodium is a free, open-source version of Visual Studio Code (VS Code) that removes Microsoft-specific telemetry and branding.
Meld: Meld is a visual diff and merge tool that helps compare files, directories, and version-controlled projects.
Ngrok: Ngrok is a tool that creates secure, temporary tunnels to expose local servers to the internet for testing and development.
Discord: Discord is a versatile communication platform for gamers and communities, offering voice, video, and text chat features.
Jitsi: Jitsi Meet is an open-source video conferencing tool that allows users to host and join secure meetings directly from their web browsers without the need for downloads.
Signal: Signal is a privacy-focused messaging app that provides end-to-end encryption for secure text, voice, and video communication.
Slack: Slack is a collaboration platform designed for team communication, featuring channels, direct messaging, file sharing, and integrations with various productivity tools.
Telegram: Telegram is a cloud-based messaging app known for its speed and security, offering features like group chats, channels, and end-to-end encrypted calls.
Zoom: Zoom is a widely-used video conferencing platform that allows users to host virtual meetings, webinars, and online collaboration with features like screen sharing and recording.
Thunderbird: Thunderbird is a free, open-source email client that offers powerful features like customizable email management, a built-in calendar, and extensive add-ons for enhanced functionality.
Brave: Brave is a free and open-source web browser developed by Brave Software, Inc. based on the Chromium web browser.
Chromium: Chromium is an open-source web browser project started by Google, to provide the source code for the proprietary Google Chrome browser.
Google Chrome: Google Chrome is a fast, secure, and free web browser, built for the modern web.
LibreWolf: LibreWolf is a fork of Firefox, focused on privacy, security, and freedom.
Lynx: Lynx is a highly configurable text-based web browser for use on cursor-addressable character cell terminals.
Mozilla Firefox: Mozilla Firefox is a free and open-source web browser developed by the Mozilla Foundation.
Thorium: Thorium is a Chromium-based browser focused on privacy and performance.
Vivaldi: Vivaldi is a freeware, cross-platform web browser developed by Vivaldi Technologies.
Alacritty: Alacritty is a modern terminal emulator that comes with sensible defaults, but allows for extensive configuration. By integrating with other applications, rather than reimplementing their functionality, it manages to provide a flexible set of features with high performance. The supported platforms currently consist of BSD, Linux, macOS and Windows. This command installs and condifures alacritty terminal emulator.
Android Debloater: Universal Android Debloater (UAD) is a tool designed to help users remove bloatware and unnecessary pre-installed applications from Android devices, enhancing performance and user experience.
Bash Prompt: The .bashrc file is a script that runs every time a new terminal session is started in Unix-like operating systems. It is used to configure the shell session, set up aliases, define functions, and more, making the terminal easier to use and more powerful. This command configures the key sections and functionalities defined in the .bashrc file from CTT's mybash repository. https://github.com/ChrisTitusTech/mybash
Bottles: Bottles allows Windows software, like applications and games, to run on Linux. Bottles also provides tools to categorize, organize and optimize your applications.
DWM-Titus: DWM is a dynamic window manager for X. It manages windows in tiled, monocle and floating layouts. All of the layouts can be applied dynamically, optimising the environment for the application in use and the task performed. This command installs and configures DWM and a desktop manager. The list of patches applied can be found in CTT's DWM repository https://github.com/ChrisTitusTech/dwm-titus
Docker: Docker is an open platform that uses OS-level virtualization to deliver software in packages called containers.
Fastfetch: Fastfetch is a neofetch-like tool for fetching system information and displaying it prettily. It is written mainly in C, with performance and customizability in mind. This command installs fastfetch and configures from CTT's mybash repository. https://github.com/ChrisTitusTech/mybash
Flatpak / Flathub: Flatpak is a universal application sandbox for Linux that uses isolated packages from Flathub to prevent conflicts and system alterations, while alleviating dependency concerns. This command installs Flatpak and adds the Flathub repository
Grub Theme: Installs ChrisTitusTech's Top 5 Bootloader Themes script to allow for easy customization of GRUB.
Kitty: kitty is a free and open-source GPU-accelerated terminal emulator for Linux, macOS, and some BSD distributions, focused on performance and features. kitty is written in a mix of C and Python programming languages. This command installs and configures kitty.
Linutil Installer: Installs a distro-specific Linutil package locally.
Linutil Updater: Updates your local Linutil crate installation.
Rofi: Rofi is a window switcher, run dialog, ssh-launcher and dmenu replacement that started as a clone of simpleswitcher, written by Sean Pringle and later expanded by Dave Davenport. This command installs and configures rofi with configuration from CTT's DWM repo. https://github.com/ChrisTitusTech/dwm-titus
Waydroid: Waydroid is an emulator that allows you to run Android apps and games on Linux.
ZSH Prompt: The Z shell is a Unix shell that can be used as an interactive login shell and as a command interpreter for shell scripting. Zsh is an extended Bourne shell with many improvements, including some features of Bash, ksh, and tcsh. This command installs ZSH prompt and provides basic configuration.
"},{"location":"userguide/#gaming","title":"Gaming","text":""},{"location":"userguide/#diablo-ii-resurrected","title":"Diablo II Resurrected","text":"
Loot Filter: This is a loot filter for Diablo II Resurrected. It's designed to be a simple, clean, and easy to read loot filter that highlights the most important items. Works on battle.net and single player. No frills, no config, just highlights high runes and other valuable items. For more information visit: https://github.com/ChrisTitusTech/d2r-loot-filter
Firewall Baselines (CTT): Developed to ease iptables firewall configuration, UFW provides a user friendly way to create an IPv4 or IPv6 host-based firewall. This command installs UFW and configures UFW based on CTT's recommended rules. For more information visit: https://christitus.com/linux-security-mistakes
Arch Server Setup: This command installs a minimal arch server setup under 5 minutes.
Paru AUR Helper: Paru is your standard pacman wrapping AUR helper with lots of features and minimal interaction. To know more about AUR helpers visit: https://wiki.archlinux.org/title/AUR_helpers
Yay AUR Helper: Yet Another Yogurt - An AUR Helper Written in Go. To know more about AUR helpers visit: https://wiki.archlinux.org/title/AUR_helpers
Configure DNF: Optimizes DNF for parallel downloads
Multimedia Codecs: This script is designed to install multimedia codecs, and to ensure RPM Fusion repositories are installed.
Nvidia Proprietary Drivers: This script is designed to download the proprietary NVIDIA drivers in Fedora.
RPM Fusion: RPM Fusion provides software that the Fedora Project or Red Hat doesn't want to ship. That software is provided as precompiled RPMs for all current Fedora versions and current Red Hat Enterprise Linux or clones versions; you can use the RPM Fusion repositories with tools like yum and PackageKit. For more information visit: https://rpmfusion.org/
Virtualization: Enables Virtualization through dnf
Build Prerequisites: This script is designed to handle the installation of various software dependencies across different Linux distributions
Full System Cleanup: This script is designed to remove unnecessary packages, clean old cache files, remove temporary files, and to empty the trash.
Full System Update: This command updates your system to the latest packages available for your distro
Gaming Dependencies: This script is designed to handle the installation of gaming dependencies across different Linux distributions
Global Theme: This script is designed to handle the installation and configuration of global theming
Remove Snaps: This script is designed to remove snap
TTY Fonts: This Script will set the default TTY font to Terminus size 32 Bold
Auto Mount Drive: This utility is designed to help with automating the process of mounting a drive on to your system.
Bluetooth Manager: This utility is designed to manage bluetooth in your system
Numlock on Startup: This utility is designed to configure auto enabling of numlock on boot
Ollama: This utility is designed to manage ollama in your system
Service Manager: This utility is designed to manage services in your system
WiFi Manager: This utility is designed to manage wifi in your system
"}]}
\ No newline at end of file
+{"config":{"lang":["en"],"separator":"[\\s\\-]+","pipeline":["stopWordFilter"]},"docs":[{"location":"","title":"Welcome to the LinUtil Documentation!","text":""},{"location":"#running-the-latest-release-of-linutil","title":"Running the latest release of LinUtil","text":"
To get started, run the following command in your terminal:
LinUtil is also available as a package in various repositories:
Arch Linux LinUtil can be installed on [Arch Linux](https://archlinux.org) with three different [AUR](https://aur.archlinux.org) packages: - `linutil` - Stable release compiled from source - `linutil-bin` - Stable release pre-compiled - `linutil-git` - Compiled from the last commit (not recommended) by running:
Replace `` with your preferred package. If you use [yay](https://github.com/Jguer/yay), [paru](https://github.com/Morganamilo/paru) or any other [AUR Helper](https://wiki.archlinux.org/title/AUR_helpers), it's even simpler:
paru -S linutil\n
Replace `paru` with your preferred helper and `linutil` with your preferred package. Cargo LinUtil can be installed via [Cargo](https://doc.rust-lang.org/cargo) with:
cargo install linutil\n
Note that crates installed using `cargo install` require manual updating with `cargo install --force` (update functionality is [included in LinUtil](https://christitustech.github.io/linutil/userguide/#applications-setup))
After you've ran the command, you should see a GUI on your screen; It will look something like this:
Info
LinUtil is updated weekly as of the time of writing. Consequently, features and functionalities may evolve, and the documentation may not always reflect the most current images or information.
Thank you for considering contributing to Linutil! We appreciate your effort in helping improve this project. To ensure that your contributions align with the goals and quality standards of Linutil, please follow these guidelines:
Make sure you have Rust installed on your machine. You can install it by following the instructions at rust-lang.org.
"},{"location":"contributing/#2-fork-and-clone-the-repo","title":"2. Fork and Clone the repo","text":"
Make a fork of the repo in GitHub
Clone the fork bash git clone https://github.com/YOUR_USERNAME_HERE/linutil.git cd linutil
"},{"location":"contributing/#3-make-your-changes","title":"3. Make your changes","text":"
Edit the files you want to change: Make your changes to the relevant files.
Test your changes: Run cargo run to test your modifications in a local environment and ensure everything works as expected.
"},{"location":"contributing/#4-understand-the-existing-code","title":"4. Understand the existing code","text":"
Have a clear reason: Don\u2019t change the way things are done without a valid reason. If you propose an alteration, be prepared to explain why it\u2019s necessary and how it improves the project.
Respect existing conventions: Changes should align with the existing code style, design patterns, and overall project philosophy. If you want to introduce a new way of doing things, justify it clearly.
"},{"location":"contributing/#5-learn-from-past-pull-requests-prs","title":"5. Learn from Past Pull Requests (PRs)","text":"
Check merged PRs: Reviewing merged pull requests can give you an idea of what kind of contributions are accepted and how they are implemented.
Study rejected PRs: This is especially important as it helps you avoid making similar mistakes or proposing changes that have already been considered and declined.
Be descriptive: Your commit messages should clearly describe what the change does and why it was made.
Use the imperative mood: For example, \"Add feature X\" or \"Fix bug in Y\", rather than \"Added feature X\" or \"Fixed bug in Y\".
Keep commits clean: Avoid committing a change and then immediately following it with a fix for that change. Instead, amend your commit or squash it if needed.
"},{"location":"contributing/#7-keep-your-pull-requests-prs-small-and-focused","title":"7. Keep Your Pull Requests (PRs) Small and Focused","text":"
Make small, targeted PRs: Focus on one feature or fix per pull request. This makes it easier to review and increases the likelihood of acceptance.
Avoid combining unrelated changes: PRs that tackle multiple unrelated issues are harder to review and might be rejected because of a single problem.
"},{"location":"contributing/#8-understand-and-test-the-code-you-write","title":"8. Understand and Test the Code You Write","text":"
Review your code: Before submitting your changes, take the time to review your code for readability, efficiency and performance. Consider how your changes affect the project.
Avoid using LLMs: Don't submit AI-generated code without reviewing and testing it first. Ensure that any code you submit is thoroughly understood and meets the project's standards.
Testing Requirements: Failure to conduct testing after multiple requests may result in the closure of your Pull Request.
"},{"location":"contributing/#9-code-review-and-feedback","title":"9. Code Review and Feedback","text":"
Expect feedback: PRs will undergo code review. Be open to feedback and willing to make adjustments as needed.
Participate in reviews: If you feel comfortable, review other contributors' PRs as well. Peer review is a great way to learn and ensure high-quality contributions.
"},{"location":"contributing/#10-contributing-is-more-than-just-code","title":"10. Contributing Is More Than Just Code","text":"
Test the tool: Running tests and providing feedback on how the tool works in different environments is a valuable contribution.
Write well-formed issues: Clearly describe bugs or problems you encounter, providing as much detail as possible, including steps to reproduce the issue.
Propose reasonable feature requests: When suggesting new features, ensure they fit within the scope, style, and design of the project. Provide clear reasoning and use cases.
Update the documentation: If your change affects the functionality, please update the relevant documentation files to reflect this.
Automatic generation: If you decide to add functionality through a new shell script, make sure to fill out all fields in tab_data.toml and run cargo xtask docgen.
Agree to the license: By contributing to Linutil, you agree that your contributions will be licensed under the project's MIT license.
We appreciate your contributions and look forward to collaborating with you to make Linutil better!
"},{"location":"faq/","title":"FAQ's","text":""},{"location":"faq/#how-do-i-uninstall-linutil","title":"How do I uninstall LinUtil?","text":"
You do not have to uninstall LinUtil. As it is a script you run from your terminal it only loads into your RAM. This means as soon as you close LinUtil it will be deleted off your system.
Focus on tasks that take time in Linux and automate them. (Example: Removing a user, adding a user, etc. - but mostly BASH scripts with POSIX compliance.)
Remove Binary linutil from being tracked in git and make it a github action.
Document every function and feature of linutil. (Preview panel description addition)
Create a discord server for linutil and invite the community.
Github Desktop: GitHub Desktop is a user-friendly application that simplifies the process of managing Git repositories and interacting with GitHub, providing a graphical interface for tasks like committing, branching, and syncing changes.
Neovim: Neovim is a refactor, and sometimes redactor, in the tradition of Vim. It is not a rewrite but a continuation and extension of Vim. This command configures neovim from CTT's neovim configuration. https://github.com/ChrisTitusTech/neovim
Sublime Text: Sublime Text is a fast, lightweight, and customizable text editor known for its simplicity, powerful features, and wide range of plugins for various programming languages.
VS Code: Visual Studio Code (VS Code) is a lightweight, open-source code editor with built-in support for debugging, version control, and extensions for various programming languages and frameworks.
VS Codium: VSCodium is a free, open-source version of Visual Studio Code (VS Code) that removes Microsoft-specific telemetry and branding.
Meld: Meld is a visual diff and merge tool that helps compare files, directories, and version-controlled projects.
Ngrok: Ngrok is a tool that creates secure, temporary tunnels to expose local servers to the internet for testing and development.
Discord: Discord is a versatile communication platform for gamers and communities, offering voice, video, and text chat features.
Jitsi: Jitsi Meet is an open-source video conferencing tool that allows users to host and join secure meetings directly from their web browsers without the need for downloads.
Signal: Signal is a privacy-focused messaging app that provides end-to-end encryption for secure text, voice, and video communication.
Slack: Slack is a collaboration platform designed for team communication, featuring channels, direct messaging, file sharing, and integrations with various productivity tools.
Telegram: Telegram is a cloud-based messaging app known for its speed and security, offering features like group chats, channels, and end-to-end encrypted calls.
Zoom: Zoom is a widely-used video conferencing platform that allows users to host virtual meetings, webinars, and online collaboration with features like screen sharing and recording.
Thunderbird: Thunderbird is a free, open-source email client that offers powerful features like customizable email management, a built-in calendar, and extensive add-ons for enhanced functionality.
Brave: Brave is a free and open-source web browser developed by Brave Software, Inc. based on the Chromium web browser.
Chromium: Chromium is an open-source web browser project started by Google, to provide the source code for the proprietary Google Chrome browser.
Google Chrome: Google Chrome is a fast, secure, and free web browser, built for the modern web.
LibreWolf: LibreWolf is a fork of Firefox, focused on privacy, security, and freedom.
Lynx: Lynx is a highly configurable text-based web browser for use on cursor-addressable character cell terminals.
Mozilla Firefox: Mozilla Firefox is a free and open-source web browser developed by the Mozilla Foundation.
Thorium: Thorium is a Chromium-based browser focused on privacy and performance.
Vivaldi: Vivaldi is a freeware, cross-platform web browser developed by Vivaldi Technologies.
Alacritty: Alacritty is a modern terminal emulator that comes with sensible defaults, but allows for extensive configuration. By integrating with other applications, rather than reimplementing their functionality, it manages to provide a flexible set of features with high performance. The supported platforms currently consist of BSD, Linux, macOS and Windows. This command installs and condifures alacritty terminal emulator.
Android Debloater: Universal Android Debloater (UAD) is a tool designed to help users remove bloatware and unnecessary pre-installed applications from Android devices, enhancing performance and user experience.
Bash Prompt: The .bashrc file is a script that runs every time a new terminal session is started in Unix-like operating systems. It is used to configure the shell session, set up aliases, define functions, and more, making the terminal easier to use and more powerful. This command configures the key sections and functionalities defined in the .bashrc file from CTT's mybash repository. https://github.com/ChrisTitusTech/mybash
Bottles: Bottles allows Windows software, like applications and games, to run on Linux. Bottles also provides tools to categorize, organize and optimize your applications.
DWM-Titus: DWM is a dynamic window manager for X. It manages windows in tiled, monocle and floating layouts. All of the layouts can be applied dynamically, optimising the environment for the application in use and the task performed. This command installs and configures DWM and a desktop manager. The list of patches applied can be found in CTT's DWM repository https://github.com/ChrisTitusTech/dwm-titus
Docker: Docker is an open platform that uses OS-level virtualization to deliver software in packages called containers.
Fastfetch: Fastfetch is a neofetch-like tool for fetching system information and displaying it prettily. It is written mainly in C, with performance and customizability in mind. This command installs fastfetch and configures from CTT's mybash repository. https://github.com/ChrisTitusTech/mybash
Flatpak / Flathub: Flatpak is a universal application sandbox for Linux that uses isolated packages from Flathub to prevent conflicts and system alterations, while alleviating dependency concerns. This command installs Flatpak and adds the Flathub repository
Grub Theme: Installs ChrisTitusTech's Top 5 Bootloader Themes script to allow for easy customization of GRUB.
Kitty: kitty is a free and open-source GPU-accelerated terminal emulator for Linux, macOS, and some BSD distributions, focused on performance and features. kitty is written in a mix of C and Python programming languages. This command installs and configures kitty.
Linutil Installer: Installs a distro-specific Linutil package locally.
Linutil Updater: Updates your local Linutil crate installation.
Rofi: Rofi is a window switcher, run dialog, ssh-launcher and dmenu replacement that started as a clone of simpleswitcher, written by Sean Pringle and later expanded by Dave Davenport. This command installs and configures rofi with configuration from CTT's DWM repo. https://github.com/ChrisTitusTech/dwm-titus
Waydroid: Waydroid is an emulator that allows you to run Android apps and games on Linux.
ZSH Prompt: The Z shell is a Unix shell that can be used as an interactive login shell and as a command interpreter for shell scripting. Zsh is an extended Bourne shell with many improvements, including some features of Bash, ksh, and tcsh. This command installs ZSH prompt and provides basic configuration.
"},{"location":"userguide/#gaming","title":"Gaming","text":""},{"location":"userguide/#diablo-ii-resurrected","title":"Diablo II Resurrected","text":"
Loot Filter: This is a loot filter for Diablo II Resurrected. It's designed to be a simple, clean, and easy to read loot filter that highlights the most important items. Works on battle.net and single player. No frills, no config, just highlights high runes and other valuable items. For more information visit: https://github.com/ChrisTitusTech/d2r-loot-filter
Firewall Baselines (CTT): Developed to ease iptables firewall configuration, UFW provides a user friendly way to create an IPv4 or IPv6 host-based firewall. This command installs UFW and configures UFW based on CTT's recommended rules. For more information visit: https://christitus.com/linux-security-mistakes
Arch Server Setup: This command installs a minimal arch server setup under 5 minutes.
Paru AUR Helper: Paru is your standard pacman wrapping AUR helper with lots of features and minimal interaction. To know more about AUR helpers visit: https://wiki.archlinux.org/title/AUR_helpers
Yay AUR Helper: Yet Another Yogurt - An AUR Helper Written in Go. To know more about AUR helpers visit: https://wiki.archlinux.org/title/AUR_helpers
Configure DNF: Optimizes DNF for parallel downloads
Multimedia Codecs: This script is designed to install multimedia codecs, and to ensure RPM Fusion repositories are installed.
Nvidia Proprietary Drivers: This script is designed to download the proprietary NVIDIA drivers in Fedora.
RPM Fusion: RPM Fusion provides software that the Fedora Project or Red Hat doesn't want to ship. That software is provided as precompiled RPMs for all current Fedora versions and current Red Hat Enterprise Linux or clones versions; you can use the RPM Fusion repositories with tools like yum and PackageKit. For more information visit: https://rpmfusion.org/
Virtualization: Enables Virtualization through dnf
Build Prerequisites: This script is designed to handle the installation of various software dependencies across different Linux distributions
Full System Cleanup: This script is designed to remove unnecessary packages, clean old cache files, remove temporary files, and to empty the trash.
Full System Update: This command updates your system to the latest packages available for your distro
Gaming Dependencies: This script is designed to handle the installation of gaming dependencies across different Linux distributions
Global Theme: This script is designed to handle the installation and configuration of global theming
Remove Snaps: This script is designed to remove snap
TTY Fonts: This Script will set the default TTY font to Terminus size 32 Bold
Auto Mount Drive: This utility is designed to help with automating the process of mounting a drive on to your system.
Bluetooth Manager: This utility is designed to manage bluetooth in your system
Numlock on Startup: This utility is designed to configure auto enabling of numlock on boot
Ollama: This utility is designed to manage ollama in your system
Service Manager: This utility is designed to manage services in your system
WiFi Manager: This utility is designed to manage wifi in your system
"}]}
\ No newline at end of file
diff --git a/sitemap.xml.gz b/sitemap.xml.gz
index 2c84ee3e9a241291be01f7306eedacddb3a3c9f8..9ed08e15c07b872bc530a077f20c3506f32cea13 100644
GIT binary patch
delta 13
Ucmb=gXP58h;9%&JoXB1Q02s9ccK`qY
delta 13
Ucmb=gXP58h;9w|YnaExN02k>4N&o-=