Download the PHP package tigron/skeleton without Composer

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

skeleton

Description

This collection of files makes up skeleton, a tiny "framework" which allows you to quickly develop small or large web applications.

We don't like to call it a framework, since it is much less than that.

Rationale

The reason why we created and maintain skeleton instead of using something more mainstream, is that we want something to suggest a certain structure and a way of working, but without getting in your way. skeleton will give you a lot of freedom to do things your way.

We re-use components from other projects whenever it makes sense. However, we will implement our own versions of simple components if that can avoid another dependency. We don't want another is-odd incident.

We have open-sourced skeleton, because we believe it may be of inspiration to others. We have chosen a very liberal license, so you are free to use it for any project you may have.

Installation

Usage

Getting started

skeleton is well suited for use without a webserver or a web front-end if that is not your thing. Likewise, it can easily be used without a database. Simply install or remove the relevant packages at will. Only the skeleton-core package is required.

That being set, the default skeleton setup comes with a few packages already required in composer.json. Feel free to add or remove any package you don't need.

To get started, have a look at the app/admin folder. You will find an example module in module/, an example event handler in event/ and some basic templates in template/.

Packages

The skeleton project is made up of loosely coupled packages. These packages implement commonly used components, tools, scripts and anything you can think of. The rule of thumb is: if you need it twice, create a package.

An overview can be found here.

Database

As with many things in skeleton you are mostly free to do what you want. But if you want things to work automagically, we expect you to follow a few simple guidelines.

Some skeleton packages will create their own tables. These tables are owned by the package. Do not add, remove or modify columns in these tables outside of the packages.

Some packages allow you to specify a table name, but most do not. If your application is already using a table with the same name as a package you want to use, you will probably need to modify your application.

Configuration and environment

Configuration is done by means of files in the config/ directory. Files are loaded in alphabetical order, with the exception of config/environment.php, which is always loaded last.

It is suggested you keep /config/environment.php out of your VCS, for example by adding it to your .gitignore file. This way, you can use it to store sensitive configuration items.

A minimal example can be seen below.

<?php
return [
    'database' => 'mysqli://username:password@localhost/database',
];

Features

Hardly any by default. Many exist as separate packages.


All versions of skeleton 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 tigron/skeleton contains the following files

Loading the files please wait ....