Download the PHP package papaya/cms-project without Composer

On this page you can find all versions of the php package papaya/cms-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?

Example code of papaya/cms-project

Informations about the package cms-project

Papaya CMS Project Skeleton

This is a project skeleton for your own papayaCMS projects. It allows to use Composer for project initialization.

It includes a build file for Phing. It uses the composer and git commands so make sure they can be called.

If you like to use the latest development versions use:

Using Phive

You can use Phive to install tools for papaya. Tools will be installed into the subdirectory tools/.

Manually

Make sure that you can call phing and run it.

Local Development Server

By default the skeleton is configured to use a SQLite 3 database and can work with the PHP built-in webserver.

Define Build Properties

Copy the file dist.build.properties to build.properties and modify it. At the moment it includes to options for database connections. One for the development and one for the deployment.

Initialize Git repository (optional)

The skeleton is optimized to be used with Git. Now would be a good point to initialize the repository.

Start the Webserver

You can use build scripts to start the webserver for your papaya CMS project on port 8080.

This will install the dependecies (composer install), update the revision file and start the PHP built-in webserver.

Open the browser at http://localhost:8080/papaya to continue the setup.

Update Project Dependencies

Install the dependencies as defined by the repository (composer.lock):

Update the dependencies (composer.json):

Because papaya CMS uses composer you can call composer install to install the dependencies defined by the repository or composer update to update them. However this will not update the revision file (Used to display project and papaya core version in administration interface).

Cloning An Existing Project

After you clone an existing project you will have to call composer install directly.

The main build file is provided by the papaya CMS core. If you clone an existing project repository the dependencies are not available so neither are the build tasks. Initially the dependencies were installed by composer create-project. So you will have to install them directly once (or if you delete the vendor directory.

Modules

Adding additional module packages:

Modules inside the project

Project specific modules can be put into the src/ directory.

Themes and Templates

Themes and templates can be composer packages, too.

Theme package will have a dependency to the template package. You do not need to require them manually. (But you can.)

Templates inside the project

Templates are installed into the templates subdirectory. You can add a new directory to your project and develop/maintain the template there.

Themes inside the project

Theme are installed into the htdocs/papaya-themes subdirectory. You can add a new directory to your project and develop/maintain the theme there.

Export the project for deployment

The build.properties (after copied from dist.build.properties) contains a property dist.database.uri that will be used for the configuration file in exports.

Additionally the exports will make use of Git tags. If the current commit is tagged this tag will be used for the file/directory name.

All versions of cms-project with dependencies

PHP Build Version
Package Version
Requires php Version >=5.6
papaya/cms-core Version ^6.7
papaya/cms-administration Version ^6.7
papaya/module-default Version 1.*
papaya/module-standard Version 1.*
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 papaya/cms-project contains the following files

Loading the files please wait ....