Skip to content
theDisco edited this page Sep 27, 2012 · 4 revisions

Directory structure

Right now Devtools became a bundle of different scripts. We have bash completion, we have shell scripts, we have resources etc. An organized directory structure have to be created, e.g.

.
|-bin
|-src
|-resources
|-tests

. directory holds README, LICENSE, package.xml, phpunit.xml and composer.json
bin directory holds all executables provided with the bundle
src holds the code necessary to run devtools
resources everything else, bash completion, twitter bootstrat, project templates etc.
tests for tests

Missing Commands

init

Right now, the only way to use Devtools is to create a project using Devtools or create a .phalcon directory in the root path of the application. init command should take care of that if I have en existing project and just want to use Devtools.

migrate

This one is self explanatory but extremely useful.

Improvements

Default Help

Right now, if you execute just phalcon without providing a command, an error will be displayed. Default behavior should be a help message.

Verbosity

As stated here

http://stackoverflow.com/questions/12612475/how-to-use-phalcon-devtools-with-an-existing-project/12614500

some people execute commands in the wrong directory. Messages displayed by Devtools have to be more verbose and provide more help to the end user.

Clone this wiki locally