automation based on phing

PhileCMS / Phile

A flat file CMS with a swappable parser and template engine.

https://philecms.github.io/

Other

257 stars 49 forks source link

automation based on phing #111

Closed Schlaefer closed 10 years ago

Schlaefer commented 10 years ago

I put together a simple build system to slim down the repository and ease the release work.

Adds phing for task management as dev composer requirement. Configuration in build.xml. Usage: run composer install as usual and call phing bash script in root.

Build system:

adds phing task to create an enduser ready .zip for homepage upload with all necessary vendor packages (specify branch and tag)
depends on git and composer installed locally
removes all "lib/vendor" code from repository

phpDoc:

adds phing task to create phpDoc
adds phpDoc as dev composer requirement
removes "docs/" from repository

NeoBlack commented 10 years ago

I am on the Road, please do not accept this request, I will reply later with more informations.

NeoBlack commented 10 years ago

now I am back at home and can give more informations. As first: many thanks @Schlaefer I love phing and your idea with the cleanup. Before we can merge this, we have to check one thing. currently we have the latest documentation available under http://philecms.com/api/ and I am not sure, but I think there is a process which get the content of /api/ from the docs folder. @james2doyle do you know the process?

Today I have refactored the bootstrapping and setup a travis ci process, we will merge this next and start then with a new development workflow. anyway, maybe we could use travis to build the phpdoc (maybe with your phing task) on each travis build.

mykiwi commented 10 years ago

Before closing #89, you should add the file composer.lock and remove it from .gitignore.

NeoBlack commented 10 years ago

I will close this pull request, please create a new one with target master branch. today we change the developer workflow. please look into our wiki for more informations. thank your for your help! please create a reference to this pull request from your new pull request.