- PHP 100%
libilling-core was a planned package that never existed. Proxmox itself is currently unused (not loaded by libilling_new's composer.json). Strip the require so the package's composer.json is valid in isolation and so a future composer install can resolve the proxmox module without choking on a missing-dependency. Also bumped the php constraint from >=8.0 to >=8.2 to match the rest of the LithiumHosting/* + LiBilling/* package set. When proxmox is wired in for real later, declare actual deps then. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| config | ||
| resources/lang | ||
| src | ||
| .gitattributes | ||
| .gitignore | ||
| composer.json | ||
| LICENSE.md | ||
| README.md | ||
LiBilling Proxmox
LiBilling component, see the package's composer.json description for the
specific role it plays in the LiBilling stack.
Installation
composer require libilling/libilling-proxmox
Source
Canonical repository: https://git.lithium.hosting/LiBilling/libilling-proxmox
License
LiBilling is (C) Lithium Holdings, LLC. All components except for third-party modules and select packages with their own license are licensed under a Commercial License. Contact licensing@lithiumholdings.com for licensing enquiries. Any dissemination of material herein is prohibited without expressed written consent of Lithium Holdings.
This package, libilling-proxmox is licensed under The MIT License (MIT). Please see License File for more information.
Is it any good?
Yes.
When people first hear about a new product, they frequently ask if it is any good. A Hacker News user remarked:
Note to self: Starting immediately, all raganwald projects will have a "Is it any good?" section in the readme, and the answer shall be "yes.".