/scripts

A list of all scripts for installing and running different tested linux services.

Primary LanguageShellGNU General Public License v3.0GPL-3.0

LINUX SCRIPTS

Description

A list of all scripts for installing and running different tested linux services.

Table of Contents

Usage

  • Clone the repository and review the script listing below.
# Clone the repository
git clone https://github.com/clonne101/scripts.git clonne-scripts

# Navigate to the project directory
cd clonne-scripts
  • Script Listing

    • clonnebots: A docker-compose setup to run and test the old Twitter APIs OLD
    • clonnedash: A docker setup to deploy a python dashboard on balena.io STALE
    • cloud9-ide: A script to setup and run the CLOUD9-IDE STALE
    • coolify: A script to setup and run Coolify.io on any VPC NEW
    • docker: A script to setup and run docker and docker-compose on Ubuntu Servers NEW
    • go_install: A script to setup and run the go-bin for Ubuntu Servers ZSH
    • pi-conn: A script to setup and share wifi-to-ethernet on a Raspberry-Pi NEW
    • proxmox: A set of scripts to setup LXC containers and also manage Alpine Containers on Proxmox NEW
    • reporterbots: A script setup to run a twitter profile, announcing its findings - old Twitter APIs OLD

Contributing

Guidelines for contributing to the project.

  1. Fork the repository.
  2. Create a new branch (git checkout -b feature/your-feature-name).
  3. Make your changes.
  4. Commit your changes (git commit -m 'Add some feature').
  5. Push to the branch (git push origin feature/your-feature-name).
  6. Open a pull request.

Submitting Issues

If you encounter any issues, have questions, or would like to suggest an enhancement, please submit an issue through the GitHub repository.

Steps to Submit an Issue

  1. Search for existing issues: Before creating a new issue, please check if the issue has already been reported.
  2. Open a new issue: If no existing issue matches your problem, open a new issue by clicking on the "New Issue" button in the Issues tab.
  3. Describe the issue: Provide a clear and concise description of the issue. Include steps to reproduce the problem, expected behavior, and actual behavior. If applicable, add screenshots or code snippets to illustrate the issue.
  4. Label the issue: Add relevant labels (e.g., bug, enhancement, question) to help categorize the issue.

License

This project is licensed under the GPLv3 License.

Code of Conduct

Please read the Code of Conduct for details.

Contact