Download the PHP package pinoox/pinroll without Composer

On this page you can find all versions of the php package pinoox/pinroll. 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?

Example code of pinoox/pinroll

Informations about the package pinroll

Pinroll — Release Rollout Engine

Pinroll (pinoox/pinroll) 1.6.8 — atomic release rollout, rollback, PinGate delivery, and blank-host provision for Pinoox.

Concept Meaning
Host Where to deploy (production, staging, …)
Bundle What to ship (auto-detect apps, or --bundle=…)
Transport How to send (ftp, ssh, pinion, local)
PinGate One public file pingate.php for install / status / rollback / vendor extract

Documentation

Full guides (setup, hosts, retention, rollback, CLI):

Install

CLI on the dev machine (recommended):

The host does not need Pinroll in vendor/. pingate.php applies releases with pincore (pinx:install / pinx:update) and Pinion.

Put Pinroll in require only if you want PinGate to use Pinroll classes on the server.

Quick start

Setup methods (no guessing)

Method When Command
Zip kit No FTP — extract into public_html php pinoox pinroll:kit
FTP Shared hosting with FTP php pinoox pinroll:connect --via=ftp
SSH VPS php pinoox pinroll:connect --via=ssh
FTP → Pinion Upload gate once, then HTTP php pinoox pinroll:connect --bootstrap-ftp

Zip kit flow:

Step Command What it does
1 pinroll:init Scaffold .pinoox/pinroll.config.php
2 pinroll:kit or pinroll:connect PinGate on host (kit / FTP / SSH)
3 pinroll:apps Set default packages for the host
4 pinroll:vendor --push Build production vendor.zip, upload, extract on host
5 pinroll:check Verify transport + PinGate
6 pinroll:deploy Build, upload, and install (go live)
7 pinroll:setup Post-deploy migrate + patch (--seed, --config)

Single-app (pinx-root): pinx deploy forwards to pinroll:deploy with this project’s package — .pinx only, not the whole project. See Deploy a Pinx app.

Subdomain folders

deploy_path is the FTP folder at account root (e.g. apps) that is linked as a subdomain. The site URL is used as entered for PinGate — path and URL are not mixed:

FTP folder Site URL Gate URL
apps https://apps.example.com https://apps.example.com/pingate.php?route=
public_html https://example.com https://example.com/pingate.php?route=
public_html/shop https://example.com/shop https://example.com/shop/pingate.php?route=

If pinroll:check reports Not PinGate JSON, upload pingate.php next to index.php and confirm the site URL matches the live domain. Do not use PATH_INFO (pingate.php/push/…); routing is ?route=.

CLI

Updates on the host use the same pincore APIs as the CLI: app/theme → PinxInstaller (pinx:install), platform/core → PlatformUpdater (pinx:update).

Tests

License

MIT — Pinoox

All versions of pinroll with dependencies

PHP Build Version
Package Version
Requires php Version ^8.2
pinoox/pinion Version ^1.1
symfony/console Version ^6.4|^7.0
symfony/http-foundation Version ^6.4|^7.0
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 pinoox/pinroll contains the following files

Loading the files please wait ...