Download the PHP package xoshbin/pertuk without Composer

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

Pertuk - Laravel Documentation Package

Latest Version on Packagist GitHub Tests Action Status GitHub Code Style Action Status Total Downloads

Pertuk is a powerful Laravel documentation package that provides a complete documentation system with multi-language support, markdown processing, search functionality, and a beautiful, responsive UI.

Features

Quick Start

  1. Install the package:

  2. Publish the assets (JS and CSS):

  3. (Optional) Publish the config:

  4. Create your docs directory and add a markdown file.

  5. Visit your docs at /docs.
  1. (Optional) Pre-render documentation for performance:

Configuration

Directory Structures

Root locale (flat) — recommended for single-language or GitHub-sourced repos

Inspired by VitePress and Starlight. One locale is designated root in config — its files live directly at the docs root with no subdirectory or URL prefix. Secondary locales keep their /{code}/ prefix.

Config:

Classic locale-prefixed — all locales in subdirectories

Omit the root key. Every locale, including the primary one, lives in its own subdirectory. This is the legacy behaviour and continues to work unchanged.

Config:

Versioned structure

Add version directories above the locale layout. Declare versions explicitly in config — no automatic directory scanning.

Config:

Monolingual (single language, no locale UI)

Configure only a root locale with no secondary entries. The language picker is hidden automatically.

Config:

GitHub Source

Pertuk can render markdown stored in a GitHub repository instead of the local filesystem. Set PERTUK_SOURCE=github and configure the repo, branch, and path. The package syncs the full directory tree into storage/app/pertuk/github/ during pertuk:build and falls back to on-demand single-file fetches at runtime.

The GitHub source works with all directory structures above — including root locale (flat) layouts. Run php artisan pertuk:build as part of your deploy to sync changes.

Migrating from the old locale config

If you are upgrading from a version that used supported_locales, default_locale, rtl_locales, and locale_labels, replace them with the unified locales map. No files need to move if you omit the root key.

Also replace exclude_versions with an explicit versions array — list only the versions you want to expose.

If you published the vendor views (php artisan vendor:publish --tag="pertuk-views"), re-publish them to get the updated templates, or replace any route('pertuk.docs.show', ['locale' => ..., 'slug' => ...]) calls with \Xoshbin\Pertuk\Support\PertukUrl::doc($slug).

Front Matter

Interactive Components (Alpine.js)

Tabs

javascript console.log("Hello World");

Accordion

Admonitions

Assets & Images

Place images in an assets/ directory at the docs root and reference them with relative paths:

Pertuk rewrites these paths to /docs/assets/filename.png automatically.

Directory conflict warning: Do not create a physical public/docs directory. In Nginx, physical directories take precedence over Laravel routes, causing 403 Forbidden errors.

Performance

Pre-render all documentation to cache during deployment:

Testing

Changelog

Please see CHANGELOG for more information on what has changed recently.

Contributing

Please see CONTRIBUTING for details.

Security Vulnerabilities

Please review our security policy on how to report security vulnerabilities.

Credits

License

The MIT License (MIT). Please see License File for more information.


All versions of pertuk with dependencies

PHP Build Version
Package Version
Requires php Version ^8.4 || ^8.3
illuminate/contracts Version ^11.0||^12.0
league/commonmark Version ^2.0
spatie/commonmark-shiki-highlighter Version ^2.5
spatie/laravel-package-tools Version ^1.16
spatie/shiki-php Version ^2.3
spatie/yaml-front-matter Version ^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 xoshbin/pertuk contains the following files

Loading the files please wait ...