Download the PHP package run-as-root/magento2-prometheus-exporter without Composer

On this page you can find all versions of the php package run-as-root/magento2-prometheus-exporter. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package magento2-prometheus-exporter

GitHub Actions Workflows

This directory contains comprehensive GitHub Actions workflows for the Magento 2 Prometheus Exporter project. These workflows ensure code quality, automate releases, and maintain project health.

🔄 Workflows Overview

1. CI (Continuous Integration) - ci.yml

Trigger: Push/PR to master or develop branches

Purpose: Core testing and quality assurance pipeline

Jobs:

2. Release - release.yml

Trigger: Git tags (v*.*.*) or manual dispatch

Purpose: Automated release management and distribution

Jobs:

3. Code Quality - code-quality.yml

Trigger: Push/PR to main branches, weekly schedule

Purpose: Comprehensive code quality analysis

Jobs:

4. Dependency Update - dependency-update.yml

Trigger: Weekly schedule (Mondays 9 AM UTC) or manual

Purpose: Automated dependency management and security monitoring

Jobs:

5. Documentation - docs.yml

Trigger: Changes to docs, README, or source code

Purpose: Documentation validation and generation

Jobs:

6. Performance Monitoring - performance.yml

Trigger: Push/PR to main branches, weekly schedule

Purpose: Performance testing and monitoring

Jobs:

🛠️ Configuration

Required Secrets

Add these secrets in your GitHub repository settings:

Required Permissions

Ensure the following permissions are enabled for GitHub Actions:

📊 Workflow Features

Automated Features

Quality Gates

Reporting

All workflows generate detailed reports in the GitHub Actions summary, including:

🚀 Getting Started

  1. Fork/Clone this repository
  2. Enable Actions in your repository settings
  3. Add Secrets (if needed for Packagist integration)
  4. Push Changes to trigger the workflows

📋 Workflow Status

You can monitor workflow status through:

Example Badges

Add these to your README.md:

🔧 Customization

Modifying Workflows

Adding Custom Checks

  1. Create new jobs in existing workflows
  2. Add custom scripts in .github/scripts/
  3. Use marketplace actions for additional functionality

🆘 Troubleshooting

Common Issues

Debug Mode

Enable debug logging by setting repository variable:

🤝 Contributing

When contributing to workflows:

  1. Test changes in a fork first
  2. Update documentation for new features
  3. Follow existing naming conventions
  4. Add appropriate error handling

📚 Additional Resources

These workflows are designed to be production-ready and can be customized based on your specific requirements.

All versions of magento2-prometheus-exporter with dependencies

PHP Build Version
Package Version
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package run-as-root/magento2-prometheus-exporter contains the following files

Loading the files please wait ....