hypernova / magento2-cloud-invoice
A Magento 2 module that stores invoices in your favorite cloud storage service
magento2-hypernova-cloud-invoice
Store Magento2 invoices into your favorite cloud storage platform.
Supports
- Google Drive
- WebDAV (Nextcloud, ownCloud)
Requirements
Google Drive
- Enable Google API for your project https://console.developers.google.com/apis/
- Create service account keys https://console.developers.google.com/apis/credentials
Nextcloud
- Create an app password
Installation
composer require hypernova/magento2-cloud-invoice
Configuration
- Go to Stores -> Configuration -> Sales -> Cloud Invoice
- Enable desired cloud platforms
-
For Google Drive, upload your service account credentials that you are able
to download right after creating a service account in Google Developer Console.
Filename is typically something like My_Project-f324uf89f3r8yfwe.json.
Also, specify Google Accounts that you want to share the invoices with. -
For Nextcloud/Owncloud, enter WebDAV URL as follows
https://NEXTCLOUD.INSTANCE.COM/remote.php/dav/files/YOUR_USERNAME
Replace NEXTCLOUD.INSTANCE.COM with your Nextcloud/Owncloud hostname, and
YOUR_USERNAME with the account you are uploading to.
Usage
Create an invoice normally via your order screen. As you create the invoice,
it will be automatically uploaded to the selected cloud storage.
Crontab (recommended)
This module can run via crontab. Go to Stores -> Configuration -> Sales ->
Cloud Invoice -> Cron settings to activate it.
Running this module via crontab prevents upload from blocking the normal
workflow of your order/invoice process.
No changelog yet
The vendor hasn't published a changelog. Tagged releases appear in the Versions tab.
| Version | Stability | QA Status | Compatibility | Released |
|---|---|---|---|---|
| 1.5.0 | stable | Fail | Magento 2.4.7-2.4.9 Details | 2026-08-22 11:15:41 |
| 1.4.0 | stable | Fail | Not yet tested Details | 2022-12-15 01:25:09 |
| 1.3.0 | stable | Not tested | Not yet tested Details | 2019-09-18 02:25:13 |
| 1.2.0 | stable | Not tested | Not yet tested Details | 2019-08-19 19:40:50 |
| 1.0.0 | stable | Not tested | Not yet tested Details | 2019-06-10 19:53:41 |
Requires 3
| Package | Constraint |
|---|---|
| google/apiclient | ^2.0 |
| php | ~5.6.5|~7.0.6|~7.1.0|~7.2.0|~7.3.0|~7.4.0|^8.1 |
| sabre/dav | * |
Compatibility
Each Magento release line is installed on its supported PHP versions, then the module is built (DI compilation + static-content deploy) and its unit and integration suites are run. The matrix shows the lines and PHP versions the module is confirmed to install and run on. Code-quality results further down (phpstan, phpcs, …) are reported separately and never affect compatibility.
Code Quality
Advisory checks against the module's source. Static analysis runs once across the whole module; PHPStan re-runs per Magento + PHP version because resolvable symbols differ between releases. These NEVER affect the Compatibility badge. A phpcs finding can't make a module incompatible.
Static analysis
Coding standards (phpcs), mess detection (phpmd), copy-pasted code (cpd), PHP cross-version compatibility, composer.json validity. Each runs once for the whole module.
PHPStan
Type-checks the module's PHP against a real Magento install at the configured gate level. Re-runs per Magento and PHP version because resolvable symbols differ between releases.
Tests
Unit and integration suites, run for each applicable Magento and PHP version. A test failure speaks to the module's behaviour, not its compatibility with a Magento line, so it is reported here separately and never reddens the compatibility matrix.
Unit tests
| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | ||
| 2.4.8 | N/A | N/A | ||
| 2.4.9 | N/A | N/A |
Integration tests
| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | ||
| 2.4.8 | N/A | N/A | ||
| 2.4.9 | N/A | N/A |
Security
Security checks run directly against the module: an audit of its declared dependencies for known vulnerabilities (composer audit) and a scan of its source for malware and web-shell signatures. Each runs once. A malware detection fails the version outright.
Turn an existing module into recurring revenue.
If you already maintain a Magento 2 module on GitHub or GitLab, listing it on Packagento takes about five minutes. We mirror your tags, handle distribution signing, and route paid licenses through Stripe Connect, so you can keep shipping the way you already do.