Download the PHP package earthit/php-template-project without Composer

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

PHP Template Project Technical Documentation

This README was automatically generated by PHPProjectInitializer. If this paragraph is still present it probably means nobody's bothered to write any project-specific documentation, yet.

See also:

Folder structure

Note that the directory is a Maven convention. It's verbose, but gives enough information to keep projects with multiple languages and components (unit tests, build system, runtime, etc) organized.

and are basically the same thing. Within one project you should probably pick one or the other and stick with it. is a Maven convention. C and JavaScript people like to call it .

Database

Create the database

If you're using Vagrant, don't do this. Just and you should be good to go. The following only applies if you want to run outside of Vagrant.

will attempt to create the database for you based on configuration in .

If that fails (due to e.g. your system is not set up in a way for which that script is designed) you can create the database yourself:

Set up a new postgres database by logging in as root ( often does the trick) and running:

If you've changed the name of the database or user in , make the corresponding changes to the above SQL.

Initialize the database

Once a database exists and permissions are set up for our user, you should be able to run , which will empty the database and rebuild it from the upgrade scripts.

Rebuilding The Database

Run to empty the database and rebuild it from the upgrade scripts in .

Run to rebuild-database the database and also adddata from .

Upgrading The Database

Run to run newly made upgrade scripts in .

Unit Testing

All tests are in

The structure of should mimic that of , where a single test file tests a single application file.

To run PHPUnit tests, run . This will run both unit and integration tests. Run to just run unit tests and to just run integration tests.

Integration tests are ones that use the database.

PHP Styles

Follow the conventions used by existing Phrebar code. Namely, tabs for leading indentation, opening brackets on the same line for functions and control structures.

(It may be that 'tabs for leading indentation' and 'Smart Tabs' refer to the exact same practice.)

Deploying

Deployment to the various environments is handled automatically by CircleCI. Read these docs about how Earthling has set up CircleCI.

Web serving

If you're using Vagrant, you can just HTTP to whatever IP address you told Vagrant to use. e.g.

http://192.168.250.250/

If you accepted the default.

If you are running Apache (and Postgres, and other required programs) on your development machine, and this directory is checked out somewhere under the DocumentRoot or an Alias, you may be able to just browse to the www directory and have things work. For me, that's

http://my-local-machine/~my-username/proj/PHPTemplateProject/www/

Most people probably need to run Vagrant though.


All versions of php-template-project with dependencies

PHP Build Version
Package Version
Requires php Version ^5.2
doctrine/dbal Version ^2.4
earthit/php-common Version ^1.1.0
earthit/dbc Version ^1.1.0
earthit/schema Version ^1.1.1
earthit/storage Version ^0.4.1
earthit/cmip-rest Version ^0.16.4
earthit/php-project-utils Version ^0.1.3
earthit/paxml Version ^1.2.1
ryprop/nife Version ^0.2.4
swiftmailer/swiftmailer Version ~5.4
togos/action Version ^1.0.0
togos/base32 Version ^1.0.1
togos/php-n2r Version ^0.1.3
togos/tpfetcher Version ^0.0.7
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 earthit/php-template-project contains the following files

Loading the files please wait ....