Download the PHP package rah/mtxpc without Composer
On this page you can find all versions of the php package rah/mtxpc. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Package mtxpc
Short Description Plugin Installer Compiler for Textpattern CMS
License GPL-2.0
Homepage https://github.com/gocom/MassPlugCompiler
FAQ
Example:
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 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.
Informations about the package mtxpc
mtxpc
mtxpc compiles Textpattern CMS plugin sources into installer packages. Supports multi-file structure and a JSON manifest file.
Install
Using Composer:
Usage
As a Library
Via Command Line
Examples:
Example Plugin Template
See abc_plugin repository for an example template.
GitHub Action
A GitHub action is available to integrating plugin compilation to automated build chain.
Plugin Template
The main difference compared to Textpattern's vanilla plugin template is how plugins are constructed. Textpattern's official template hosts everything in a single file, while mtxpc splits the sources to separate files; translations, readme, manifest and source code.
Translations
Textpacks, Textpattern's plugin localization files, can be stored in a single file, or as separate files, each file storing a different language. The compiler searches .textpack files from a directory named textpacks.
Textpattern offers a way to set the default language which is used as the fallback when the plugin doesn't come with user's language. The default language is chosen based on #@language keyword, or lack of. Textpack files that do not define a language, are treated as the default fallback. Compare abc_plugin's en-gb.texpack and fi-fi.textpack files. The en-gb doesn't define the language code and is set as the default.
Manifest
The manifest file, manifest.json, contains all plugin's meta data. That's the rest of the stuff a plugin is made of, including plugin's version number, author, url, special flags, type, and recommended loading order.
Help File
Manifest file can also be used to specify help file's location. By default a help file is expected to be named as help with any extension, but a different location can be chosen with a file option:
Textile markup can be used in the help file. If the help file's filename ends with .textile extension, or the file contents start with h1. tag, the file is treated as if it contained Textile markup.
Development
See CONTRIBUTING.md.
All versions of mtxpc with dependencies
ext-json Version *
ext-mbstring Version *
ext-pcre Version *
ext-zlib Version *