Download the PHP package darling/darlingdatamanagementsystem without Composer

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

Roady logo

Development of Roady v2.0

Roady is a php framework I have been developing for a long time. At this point it is a passion project. I love coding, working on Roady makes me happy.

Roady v1.1.2 is the current stable version of Roady, and can be found here:

https://github.com/sevidmusic/roady/releases/tag/v1.1.2

Roady v2.0 is a complete re-write of Roady that will be influenced by Roady's original design, but will not be compatible with previous versions of Roady.

Note: At the moment I am using this file to plan the rest of the re-write of Roady2.0. This file will be revised to document Roady2.0 before Roady2.0 is released.

Note: This document is still being drafted, and will continue to evolve over time.

About

Roady is a modular php framework.

With Roady the features and functionality of a website are implemented by individual Modules.

For example, say my band used Roady to build our website, and we needed a music player, that music player would be implemented by a Module.

If we needed a calender to show upcoming gigs, it would be implemented by a different Module.

Multiple websites can run on a single installation of Roady, each making use of one or more installed Roady Modules.

Modules

Anatomy of a Module

Directory Description
css This is where css stylesheets should be located.
js This is where javascript files should be located.
output This is where php and html files should be located.
APPROPRIATE.SITE.AUTHORITY.json This file defines hard-coded Routes for a specific website.

How a Module Works

Modules should be located in Roady's modules directory.

Modules may define output to be displayed via Roady's UI in the form of html or php files.

Modules may define css stylesheets and javascript files to define styles and implement additional functionality for a website.

Modules may serve php, html, css, and javascript, in Response to a Request to a website via the Routes defined in a json file which is named after the website's Domain's Authority.

For example, sub.example.com.8080.json would be the name of the json file used to define Routes for a website with the following Domain:

Using a website's Domain's Authority to name Route configuration files allows Modules to define unique Routes for each website.

Routes

A Route defines the following:

For example, the following json defines a single Route to a html file named output-file.html:

Roady's User Interface (UI)

Roady's UI uses the Routes defined by installed Modules to determine the html that should be rendered in Response to a Request.

Roady's UI uses the Named Positions provided by an internally defined html layout to structure the collective output of Routes that respond to the same Request:

The following table is an overview of the purpose of each of the Named Positions provided by Roady's UI's internally defined html layout:

Named Position Purpose
<roady-ui-page-title-placeholder> This position name is reserved for internal use, Roady's UI determines the page title based on the Request that was made.
<roady-ui-meta-description> For description meta data that should be rendered in the value attribute of a <meta> tag in the <head> section of the output Rendered by Roady's UI.
<roady-ui-meta-keywords> For keyword meta data that should be rendered in the value attribute of a <meta> tag in the <head> section of the output Rendered by Roady's UI.
<roady-ui-meta-author> For author meta data that should be rendered in the value attribute of a <meta> tag in the <head> section of the output Rendered by Roady's UI.
<roady-ui-css-stylesheet-link-tags> For <link> tags rendered for Routes to css stylesheets.
<roady-ui-js-script-tags-for-html-head> For <script> tags rendered for Routes to javascropt files.
<roady-ui-pre-header> For output that shoud be rendered before the <header>.
<roady-ui-header> For output that should be rendered within the <header>.
<roady-ui-main-content> For output that should be rendered within <main>.
<roady-ui-footer> For output that should be rendered within the <footer>.
<roady-ui-js-script-tags-for-end-of-html> For Routes to javascript files that should be loaded after the closing <body> tag.

All versions of darlingdatamanagementsystem with dependencies

PHP Build Version
Package Version
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 darling/darlingdatamanagementsystem contains the following files

Loading the files please wait ....