Libraries tagged by file path
dzunke/panaly-codeowners
7 Downloads
A Panaly plugin that makes it able to write paths from a CODEOWNERS file to metrics
daku/nette-webpack-manifest
5 Downloads
Provides Latte functions for reading asset paths from Webpack manifest file.
secra/caching-proxy
16 Downloads
Converts a bunch of .css/.js files to one minified file and precompress them with gzip. Rewrite all relative path of ressources in css files.
flyke/laravel-template-hints
54 Downloads
Show the paths to current blade template files in html source for finding the correct template
ftm-pm/media-server
0 Downloads
MediaServer is a micro application that receives an image file with filters and returns the path to this image and a collection of images with applied filters.
mvccore/ext-view-helper-dataurl
56 Downloads
MvcCore - Extension - View - Helper - Data URL - get any file content by given relative or absolute path in data url format: `data:image/png;base64,iVBOR..`.
cosmin-ciolacu/zipper
11 Downloads
A simple zip utility for creating zip files and extracting items to a specific path
truecastdesign/jsonredirects
11 Downloads
Json file based redirects with exact match and wildcard * matching for changing higher up paths with sub categories so the sub categories get redirected as well.
sramage/pictured
7 Downloads
Simple picture and video file sorting service/daemon for linux written in PHP. It takes photos & videos from a source directory and sorts the photos into Y/M folders and the videos into Y folders (ie. dest_path/2014/January).
sarverott/rokita
0 Downloads
new Controll Panel of New Order, tool to manage your host. Uploaded on server allows you to use path traversal, using easy-to-use filesystem explorer. Tools to upload files, php eval and shell execution are also onboard.
pcual-mac/image-basekit-cli
0 Downloads
Small CLI app that handles image storage to be used as part of a wider application. You can assume actual capture of the image happens elsewhere in the wider application and the local path to an image can simply be passed as input to the CLI app. The app should perform basic validation on the image and allow it’s storage, retrieval and deletion on the file system. Note whilst only file system storage is required in this test the module should be written in such a way that makes it easy to plug in future required storage methods eg S3, FTP etc using just a config change along with the new storage class.
lcsng/amanda
7 Downloads
Amanda is a lightweight and flexible PHP routing library that dynamically maps website URLs to template files without requiring manual route definitions or directory structures. Simply place your .php or .html templates inside the amanda_templates/ directory, and Amanda will automatically serve them based on the requested URL. Easily customize template paths, override defaults, and streamline page routing for faster, more efficient web development.
jarlssen/cmsfiles
238 Downloads
Jarlssen_CmsFiles will allow you to create files (versioned with your favourite SCM tool) in a path of your choice
geshan/pdepend-analyzer
277 Downloads
Pdepend Analyze is a command line tool that analyzes the summary xml file generated by PHP Depend like cyclomatic complexity and N-Path complexity
fwrepae/fwrepae
0 Downloads
The Inter TT REST API is described using OpenAPI 3.0. The descriptor for the api can be downloaded in both [YAML](http://localhost:8080/cyclos/api/openapi.yaml) or [JSON](http://localhost:8080/cyclos/api/openapi.json) formats. These files can be used in tools that support the OpenAPI specification, such as the [OpenAPI Generator](https://openapi-generator.tech). In the API, whenever some data is referenced, for example, a group, or payment type, either id or internal name can be used. When an user is to be referenced, the special word 'self' (sans quotes) always refers to the currently authenticated user, and any identification method (login name, e-mail, mobile phone, account number or custom field) that can be used on keywords search (as configured in the products) can also be used to identify users. Some specific data types have other identification fields, like accounts can have a number and payments can have a transaction number. This all depends on the current configuration. ----------- Most of the operations that return data allow selecting which fields to include in the response. This is useful to avoid calculating data that finally won't be needed and also for reducing the transfer over the network. If nothing is set, all object fields are returned. Fields are handled in 3 modes. Given an example object `{"a": {"x": 1, "y": 2, "z": 3}, "b": 0}`, the modes are: - **Include**: the field is unprefixed or prefixed with `+`. All fields which are not explicitly included are excluded from the result. Examples: - `["a"]` results in `{"a": {"x": 1, "y": 2, "z": 3}}` - `["+b"]` results in `{"b": 0}` - `["a.x"]` results in `{"a": {"x": 1}}`. This is a nested include. At root level, includes only `a` then, on `a`'s level, includes only `x`. - **Exclude**: the field is prefixed by `-` (or, for compatibility purposes, `!`). Only explicitly excluded fields are excluded from the result. Examples: - `["-a"]` results in `{"b": 0}` - `["-b"]` results in `{"a": {"x": 1, "y": 2, "z": 3}}` - `["a.-x"]` results in `{"a": {"y": 2, "z": 3}}`. In this example, `a` is actually an include at the root level, hence, excludes `b`. - **Nested only**: when a field is prefixed by `*` and has a nested path, it only affects includes / excludes for the nested fields, without affecting the current level. Only nested fields are configured. Examples: - `["*a.x"]` results in `{"a": {"x": 1}, "b": 0}`. In this example, `a` is configured to include only `x`. `b` is also included because, there is no explicit includes at root level. - `["*a.-x"]` results in `{"a": {"y": 2, "z": 3}, "b": 0}`. In this example, `a` is configured to exclude only `x`. `b` is also included because there is no explicit includes at the root level. For backwards compatibility, this can also be expressed in a special syntax `-a.x`. Also, keep in mind that `-x.y.z` is equivalent to `*x.*y.-z`. You cannot have the same field included and excluded at the same time - a HTTP `422` status will be returned. Also, when mixing nested excludes with explicit includes or excludes, the nested exclude will be ignored. For example, using `["*a.x", "a.y"]` will ignore the `*a.x` definition, resulting in `{"a": {"y": 2}}`. ----------- For details of the deprecated elements (operations and model) please visit the [deprecation notes page](https://documentation.cyclos.org/4.16.3/api-deprecation.html) for this version.