Download the PHP package webware/webware-tools without Composer
On this page you can find all versions of the php package webware/webware-tools. 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:
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.
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 webware-tools
webware/webware-tools
Shared CI/CD and tooling configuration for the Webware package family. Consumed as a dev dependency by every component; it ships no PHP code.
What ships
| Path | Purpose |
|---|---|
mago.toml |
The central Mago configuration every component extends. The Mago version is pinned here, in version =, and nowhere else. |
mago-analysis-types.md |
Docblock-only types Mago's analyzer understands. |
mago-guard-realignment.md |
Procedure for a consumer dropping local guard overrides in favour of the central rules. |
presets/webware-alignment/ |
Spec-Kit preset: templates and ready-to-copy artifacts for aligning a package. See its README. |
How a consumer uses it
- Mago — the package's own
mago.tomlis a stub that extends this one (extends = "vendor/webware/webware-tools/mago.toml"). General settings and the ecosystem-wide guard rules are central; only a domain-specific rule belongs locally. - CI — the pipeline is the organization's required workflow, bound to every repository by the
organization ruleset. A package varies it with
webware-ci.jsonin its own root. There is no per-package workflow file and no workflow ref to keep in sync. - Containers — the tooling
Dockerfilederives the Mago version from this file'sversion =pin, resolved through the consumer'scomposer.lock, so the tool inside the container always matches the pin Mago itself enforces.
The pin has exactly one home
version = in mago.toml is the only place a Mago version is written in the ecosystem. The
required workflow rejects a copy of it in any of these forms:
- a Dockerfile
ARG MAGO_VERSION= - a compose build argument
- a workflow
tools: mago:<version> - a
mago.tomlversion = - a version-pinned Mago schema URL (
#:schema …/x.y.z/schema.json)
A Mago bump is therefore one line in one file, and every consumer container and CI job follows it
through the revision its own composer.lock resolves.
License
BSD-3-Clause. See LICENSE.
All versions of webware-tools with dependencies
PHP Build Version
Package Version
Requires
php Version
~8.4.0 || ~8.5.0
The package webware/webware-tools contains the following files
Loading the files please wait ...