Skip to content

πŸš€ Reusable GitHub Actions for MBBe-Software organization - Docker setup, deployment utilities, and common CI/CD operations

Notifications You must be signed in to change notification settings

MBBe-Software/actions

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

1 Commit
Β 
Β 
Β 
Β 

Repository files navigation

πŸš€ MBBe-Software Actions

Centralized repository for reusable GitHub Actions used across MBBe-Software organization projects.

πŸ“¦ Available Actions

🐳 docker-setup

Install and configure Docker on remote servers via SSH with production-grade configuration.

- name: Setup Docker on Server
  uses: MBBe-Software/actions/docker-setup@v1
  with:
    host: ${{ secrets.SERVER_IP }}
    username: ${{ secrets.SERVER_USERNAME }}
    ssh-key: ${{ secrets.SSH_PRIVATE_KEY }}
    docker-version: 'latest'  # optional
    compose-plugin: true      # optional

Features:

  • βœ… Intelligent Docker installation detection
  • βœ… Official Docker repository with GPG verification
  • βœ… Production-grade daemon configuration
  • βœ… Docker Compose plugin installation
  • βœ… Comprehensive error handling and logging
  • βœ… Health verification and testing

πŸ—οΈ Repository Structure

actions/
β”œβ”€β”€ docker-setup/           # Docker installation action
β”‚   β”œβ”€β”€ action.yml          # Action definition
β”‚   └── README.md           # Action documentation
β”œβ”€β”€ future-action/          # Future actions will go here
β”‚   β”œβ”€β”€ action.yml
β”‚   └── README.md
└── README.md              # This file

🎯 Usage Philosophy

Each action in this repository follows these principles:

  1. πŸ”’ Security First: Secure secret handling and validation
  2. πŸš€ Production Ready: Tested in real production environments
  3. πŸ“ Well Documented: Clear usage examples and parameters
  4. πŸ”„ Reusable: Works across different projects and environments
  5. πŸ›‘οΈ Error Handling: Comprehensive error checking and reporting
  6. πŸ“Š Logging: Detailed execution logs for debugging

🀝 Contributing

When adding new actions:

  1. Create a new directory for each action
  2. Include action.yml with proper metadata
  3. Add comprehensive README.md with usage examples
  4. Test thoroughly before tagging versions
  5. Follow semantic versioning for releases

🏷️ Versioning

  • Use semantic versioning: v1.0.0, v1.1.0, etc.
  • Tag major versions: v1, v2 for easier consumption
  • Document breaking changes in releases

πŸ€– Generated with Claude Code

About

πŸš€ Reusable GitHub Actions for MBBe-Software organization - Docker setup, deployment utilities, and common CI/CD operations

Resources

Stars

Watchers

Forks

Packages

No packages published

Contributors 2

  •  
  •