PHPackages                             papaya/cms-project - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Framework](/categories/framework)
4. /
5. papaya/cms-project

ActiveLibrary[Framework](/categories/framework)

papaya/cms-project
==================

papaya CMS Project Skeleton

1.10.0(7y ago)24061GPL-2.0PHPPHP >=5.6

Since May 23Pushed 5y ago6 watchersCompare

[ Source](https://github.com/papayaCMS/papayacms-project)[ Packagist](https://packagist.org/packages/papaya/cms-project)[ Docs](http://www.papaya-cms.com/)[ RSS](/packages/papaya-cms-project/feed)WikiDiscussions master Synced 1mo ago

READMEChangelog (10)Dependencies (6)Versions (13)Used By (0)

Papaya CMS Project Skeleton
===========================

[](#papaya-cms-project-skeleton)

This is a project skeleton for your own [papayaCMS](http://www.papaya-cms.com) projects. It allows to use [Composer](http://getcomposer.org) for project initialization.

It includes a build file for [Phing](http://www.phing.info). It uses the `composer` and `git` commands so make sure they can be called.

```
composer create-project papaya/cms-project projectname

```

If you like to use the latest development versions use:

```
composer create-project papaya/cms-project projectname -s dev

```

Using Phive
-----------

[](#using-phive)

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

```
cd projectname
phive install
composer install
tools/phing

```

Manually
--------

[](#manually)

Make sure that you can call `phing` and run it.

```
cd projectname
composer install
phing

```

Local Development Server
------------------------

[](#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

[](#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)

[](#initialize-git-repository-optional)

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

```
git init
git add *
git commit -m"new project"

```

### Start the Webserver

[](#start-the-webserver)

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

```
phing run

```

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

[](#update-project-dependencies)

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

```
phing dependencies-install

```

Update the dependencies (composer.json):

```
phing dependencies-update

```

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

[](#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
-------

[](#modules)

Adding additional module packages:

```
composer require papaya/module-domains

```

### Modules inside the project

[](#modules-inside-the-project)

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

Themes and Templates
--------------------

[](#themes-and-templates)

Themes and templates can be composer packages, too.

```
composer require papaya/theme-dynamic

```

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-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

[](#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
---------------------------------

[](#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.

```
phing export

```

###  Health Score

31

—

LowBetter than 68% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity17

Limited adoption so far

Community10

Small or concentrated contributor base

Maturity65

Established project with proven stability

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~161 days

Recently: every ~91 days

Total

12

Last Release

2601d ago

### Community

Maintainers

![](https://avatars.githubusercontent.com/u/236825?v=4)[Thomas Weinert](/maintainers/ThomasWeinert)[@ThomasWeinert](https://github.com/ThomasWeinert)

---

Top Contributors

[![ThomasWeinert](https://avatars.githubusercontent.com/u/236825?v=4)](https://github.com/ThomasWeinert "ThomasWeinert (39 commits)")

---

Tags

cmscontent-managementcontent-management-systemphpxslxslt

### Embed Badge

![Health badge](/badges/papaya-cms-project/health.svg)

```
[![Health](https://phpackages.com/badges/papaya-cms-project/health.svg)](https://phpackages.com/packages/papaya-cms-project)
```

###  Alternatives

[laravel/telescope

An elegant debug assistant for the Laravel framework.

5.2k67.8M192](/packages/laravel-telescope)[spiral/roadrunner

RoadRunner: High-performance PHP application server and process manager written in Go and powered with plugins

8.4k12.2M84](/packages/spiral-roadrunner)[nolimits4web/swiper

Most modern mobile touch slider and framework with hardware accelerated transitions

41.8k177.2k1](/packages/nolimits4web-swiper)[laravel/dusk

Laravel Dusk provides simple end-to-end testing and browser automation.

1.9k36.7M259](/packages/laravel-dusk)[laravel/prompts

Add beautiful and user-friendly forms to your command-line applications.

708181.8M596](/packages/laravel-prompts)[cakephp/chronos

A simple API extension for DateTime.

1.4k47.7M121](/packages/cakephp-chronos)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)