Download the PHP package ginger-tek/jerpy without Composer

On this page you can find all versions of the php package ginger-tek/jerpy. 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 jerpy

jerpy

Small | Zero Dependencies | Flat-file


Jerpy a small, zero-dependency, flat-file simple website system built for control and simplicity that is easy to install, customize, and maintain.

Jerpy doesn't have a management interface or web portal (there could be a plugin for that...). Everything is managed directly via the files themselves.

Getting Started

Composer

Files & Folders

Pages & Routes

Routes are configured in an associative array of a route key and page value. The value can be either a string or an associative array. If a string, the value is rendered using the default template, and the string is expected to be the filename of a page in the pages folder. If an associative array, there must be at least a page key and value. Optionally, a meta key and value can be set to include metadata for the given route, as well as a layout key and value to override the default layout, or not use one at all.

Example routes config:

When implementing metadata, use the @ warning suppression syntax to avoid warnings when a route does't have that metadata property specified:

Dynamic Routes

To use dynamic route parameters, use the :param syntax in the route key string. All matches values will be accessible from the $params variable:

product.php:

Templating

PHP's built-in templating is sufficient for most websites. As such, just use include and require as you would normally for templating your site, parsing content as needed (see plugins).

Global Variables

Name Data Type Note
$uri object Clean URI value
$params array Any metadata key/values specified for the matched route
$page string Path to the page file being rendered
$meta array Any metadata key/values specified for the matched route
$layout array Current layout

Plugins

Plugins can be created to extend or add functionality to Jerpy. They do not require any specific framework nor follow any particular design pattern. The only requirement for plugins is that the entrypoint is a .php file with the same name as the plugin's folder. From there, you can use whatever preferred tools and package managers to create the plugin code, such as Composer.

Plugins can be included/required on a given page file as needed, or you can load it globally to be used on every page. To add a plugin, simply copy/upload the plugin's folder to the plugins directory. To enable a plugin globally, add it's folder name to the $plugins array in config.php.

Below is an example plugin for using Parsedown via a wrapper method:

NOTE: When including/requiring files within a plugin, make sure to use the __DIR__ global to ensure PHP looks within the plugin directory and not in the root directory of the site

plugins/md/md.php

config.php

pages/some-page.php


All versions of jerpy with dependencies

PHP Build Version
Package Version
Requires php Version >=8.2.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 ginger-tek/jerpy contains the following files

Loading the files please wait ....