Download the PHP package open-foundations/kirby-base without Composer

On this page you can find all versions of the php package open-foundations/kirby-base. 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 kirby-base

kirby-base

Shared Kirby plugin used by several BSBI sites. Released by git tag; consumers pin an exact version in their own composer.json.

Consuming sites must provide these dependencies themselves

This plugin declares runtime dependencies in its own composer.json:

Package Why
setasign/fpdi reads an existing PDF so a certificate can be overlaid onto the designer's artwork
tecnickcom/tcpdf writes the PDF; UTF-8 native, so names like Siân or Ó Briain survive
league/flysystem, league/flysystem-aws-s3-v3, league/flysystem-memory document storage (BSBI\WebBase\storage): local, S3, and in-memory for tests — see documentation/document-storage.md

How those reach the site depends on how the plugin is being used, and the two differ:

What a consuming site should do

Declare them in the site's own composer.json and install with a targeted update:

Targeted, never a bare composer update: this plugin is installed to site/plugins/kirby-base, the same path as the submodule, so an untargeted run deletes the submodule working tree.

This duplicates our requirement into each consuming site, which is not lovely. It is deliberate: the alternative is for this plugin to require its own vendor/autoload.php, and it must not. Our require-dev includes getkirby/cms, so that directory holds a second Kirby, and Composer's generated autoloader registers with prepend = true — loading it would put the wrong Kirby ahead of the site's for every class not yet loaded. Two declared lines beat that.

Working on this plugin

See CLAUDE.md for the development workflow, testing and version management.

All versions of kirby-base with dependencies

PHP Build Version
Package Version
Requires php Version >=8.3.0 <8.5.0
ext-pdo Version *
getkirby/composer-installer Version ^1.2
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 open-foundations/kirby-base contains the following files

Loading the files please wait ...