Real initial commit
Signed-off-by: Sebastian Cabrera <okseby@protonmail.com>
This commit is contained in:
parent
67e61d84c3
commit
98b272f922
2 changed files with 163 additions and 68 deletions
113
README.md
113
README.md
|
|
@ -1,93 +1,70 @@
|
|||
# crunchbang
|
||||
|
||||
A collection of useful bash scripts to enhance your command-line experience and automate common tasks.
|
||||
|
||||
## 🚀 Overview
|
||||
|
||||
## Getting started
|
||||
This repository contains a curated set of bash scripts that can help streamline your workflow, automate repetitive tasks, and make your command-line experience more efficient. Each script is well-documented and designed to be easily integrated into your daily routine.
|
||||
|
||||
To make it easy for you to get started with GitLab, here's a list of recommended next steps.
|
||||
## 📦 Installation
|
||||
|
||||
Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
|
||||
|
||||
## Add your files
|
||||
|
||||
- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
|
||||
- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
|
||||
|
||||
```
|
||||
cd existing_repo
|
||||
git remote add origin https://git.okseby.com/okseby/crunchbang.git
|
||||
git branch -M main
|
||||
git push -uf origin main
|
||||
1. Clone the repository:
|
||||
```bash
|
||||
git clone https://git.okseby.com/okseby/crunchbang.git
|
||||
cd crunchbang
|
||||
```
|
||||
|
||||
## Integrate with your tools
|
||||
2. Make the scripts executable:
|
||||
```bash
|
||||
chmod +x scripts/*.sh
|
||||
```
|
||||
|
||||
- [ ] [Set up project integrations](https://git.okseby.com/okseby/crunchbang/-/settings/integrations)
|
||||
3. (Optional) Add the scripts directory to your PATH:
|
||||
```bash
|
||||
echo 'export PATH="$PATH:$(pwd)/scripts"' >> ~/.bashrc
|
||||
# or for zsh
|
||||
echo 'export PATH="$PATH:$(pwd)/scripts"' >> ~/.zshrc
|
||||
```
|
||||
|
||||
## Collaborate with your team
|
||||
## 🛠️ Available Scripts
|
||||
|
||||
- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
|
||||
- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
|
||||
- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
|
||||
- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
|
||||
- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
|
||||
Each script in this collection serves a specific purpose. Here's a brief overview of what's available:
|
||||
|
||||
## Test and Deploy
|
||||
- `scripts/`: Directory containing all the bash scripts
|
||||
- (Scripts will be listed here as they are added)
|
||||
|
||||
Use the built-in continuous integration in GitLab.
|
||||
## 📖 Usage
|
||||
|
||||
- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
|
||||
- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
|
||||
- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
|
||||
- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
|
||||
- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
|
||||
Each script includes its own documentation and usage instructions. You can view the help for any script by running:
|
||||
|
||||
***
|
||||
```bash
|
||||
./scripts/script-name.sh --help
|
||||
```
|
||||
|
||||
# Editing this README
|
||||
## 🤝 Contributing
|
||||
|
||||
When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
|
||||
Contributions are welcome! If you have a useful bash script that you'd like to share:
|
||||
|
||||
## Suggestions for a good README
|
||||
1. Fork the repository
|
||||
2. Create a new branch for your feature
|
||||
3. Add your script to the `scripts/` directory
|
||||
4. Update the README with information about your script
|
||||
5. Submit a pull request
|
||||
|
||||
Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
|
||||
Please ensure your scripts:
|
||||
- Include proper documentation
|
||||
- Follow bash best practices
|
||||
- Include error handling
|
||||
- Are tested thoroughly
|
||||
|
||||
## Name
|
||||
Choose a self-explaining name for your project.
|
||||
## 📝 License
|
||||
|
||||
## Description
|
||||
Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
|
||||
This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
|
||||
|
||||
## Badges
|
||||
On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
|
||||
## ⭐ Support
|
||||
|
||||
## Visuals
|
||||
Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
|
||||
If you find these scripts useful, please consider giving the repository a star! For issues, feature requests, or questions, please open an issue in the GitLab repository.
|
||||
|
||||
## Installation
|
||||
Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
|
||||
---
|
||||
|
||||
## Usage
|
||||
Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
|
||||
|
||||
## Support
|
||||
Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
|
||||
|
||||
## Roadmap
|
||||
If you have ideas for releases in the future, it is a good idea to list them in the README.
|
||||
|
||||
## Contributing
|
||||
State if you are open to contributions and what your requirements are for accepting them.
|
||||
|
||||
For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
|
||||
|
||||
You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
|
||||
|
||||
## Authors and acknowledgment
|
||||
Show your appreciation to those who have contributed to the project.
|
||||
|
||||
## License
|
||||
For open source projects, say how it is licensed.
|
||||
|
||||
## Project status
|
||||
If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
|
||||
Made with ❤️ by [Your Name]
|
||||
|
|
|
|||
118
movefiles.sh
Executable file
118
movefiles.sh
Executable file
|
|
@ -0,0 +1,118 @@
|
|||
#!/bin/bash
|
||||
|
||||
# Default values
|
||||
VERBOSE=false
|
||||
INCLUDE_PART=false
|
||||
|
||||
# Function to display usage
|
||||
usage() {
|
||||
echo "Usage: $0 [options] <search_word> <source_directory> <destination_directory>"
|
||||
echo "Options:"
|
||||
echo " -v, --verbose Show detailed output"
|
||||
echo " -p, --include-part Include files ending in .part (excluded by default)"
|
||||
echo " -h, --help Show this help message"
|
||||
exit 1
|
||||
}
|
||||
|
||||
# Parse command line options
|
||||
while [[ $# -gt 0 ]]; do
|
||||
case $1 in
|
||||
-v|--verbose)
|
||||
VERBOSE=true
|
||||
shift
|
||||
;;
|
||||
-p|--include-part)
|
||||
INCLUDE_PART=true
|
||||
shift
|
||||
;;
|
||||
-h|--help)
|
||||
usage
|
||||
;;
|
||||
*)
|
||||
break
|
||||
;;
|
||||
esac
|
||||
done
|
||||
|
||||
# Check if we have exactly 3 arguments after options
|
||||
if [ "$#" -ne 3 ]; then
|
||||
usage
|
||||
fi
|
||||
|
||||
SEARCH_WORD=$1
|
||||
SOURCE_DIR=$2
|
||||
DEST_DIR=$3
|
||||
|
||||
# Validate search word
|
||||
if [ -z "$SEARCH_WORD" ]; then
|
||||
echo "Error: Search word cannot be empty"
|
||||
exit 1
|
||||
fi
|
||||
|
||||
# Ensure source directory exists
|
||||
if [ ! -d "$SOURCE_DIR" ]; then
|
||||
echo "Error: Source directory '$SOURCE_DIR' does not exist."
|
||||
exit 1
|
||||
fi
|
||||
|
||||
# Initialize counter
|
||||
moved_count=0
|
||||
|
||||
# Function to process files
|
||||
process_files() {
|
||||
local find_cmd="find \"$SOURCE_DIR\" -maxdepth 1 -type f -iname \"*$SEARCH_WORD*\""
|
||||
|
||||
# Exclude .part files and macOS resource fork files by default
|
||||
if [ "$INCLUDE_PART" = false ]; then
|
||||
find_cmd="$find_cmd -not -name \"*.part\""
|
||||
fi
|
||||
find_cmd="$find_cmd -not -name \"._*\""
|
||||
|
||||
# First, show what would be moved
|
||||
echo "The following files would be moved:"
|
||||
eval "$find_cmd"
|
||||
|
||||
# Count files that would be moved
|
||||
local file_count=$(eval "$find_cmd" | wc -l)
|
||||
|
||||
if [ "$file_count" -eq 0 ]; then
|
||||
echo "No matching files found."
|
||||
exit 0
|
||||
fi
|
||||
|
||||
# Show what actions will be taken
|
||||
echo
|
||||
if [ ! -d "$DEST_DIR" ]; then
|
||||
echo "The destination directory '$DEST_DIR' will be created."
|
||||
fi
|
||||
echo "Files will be moved to: '$DEST_DIR'"
|
||||
|
||||
# Prompt for confirmation
|
||||
echo -n "Do you want to proceed? (y/n): "
|
||||
read -r response
|
||||
|
||||
if [[ "$response" =~ ^[Yy]$ ]]; then
|
||||
# Create destination directory if needed
|
||||
if [ ! -d "$DEST_DIR" ]; then
|
||||
mkdir -p "$DEST_DIR"
|
||||
fi
|
||||
|
||||
while IFS= read -r file; do
|
||||
if [ "$VERBOSE" = true ]; then
|
||||
echo "Moving: $file"
|
||||
fi
|
||||
if mv "$file" "$DEST_DIR"; then
|
||||
((moved_count++))
|
||||
else
|
||||
echo "Error: Failed to move '$file'" >&2
|
||||
fi
|
||||
done < <(eval "$find_cmd")
|
||||
|
||||
echo "Operation completed. $moved_count file(s) moved to '$DEST_DIR'"
|
||||
else
|
||||
echo "Operation cancelled."
|
||||
fi
|
||||
}
|
||||
|
||||
# Execute the move operation
|
||||
process_files
|
||||
Loading…
Add table
Add a link
Reference in a new issue