Re: suggestion for deployment

Hey Lorenzo,

One idea would be to have an installer where they answer a few basic
questions and then it will make some configuration files. What you
could do is have your database.php file read the settings file that is
made by the installer. Then they can keep all their configurations
they set. You could also have your app_controller read in the
settings file as well.

I'm in the process of rewriting the http://dam.gd system and it will
utilize cakePHP in version 2.0. We will be releasing version 1.1 in
the new week or so and it will incorporate a great new system from
http://theeasyapi.com ... now they haven't fully launched but they let
us in on the code so we could start to build it in. It's pretty
freaking cool. Accessing multiple API's with just one API and
everything is fully controlled and documented. The developers are
really nice as well.

Take care.

On Jan 16, 12:13 pm, Lorenzo Bettini <bett...@dsi.unifi.it> wrote:
> Hi
>
> I'd like to distribute a package which uses cakephp, so I'm distributing
> both app and cake directories.
>
> Now I'd like to know what the right way of distributing files is, in
> particular in such a way that when I distribute another version the user
> does not loose his own configurations.
>
> For instance, for database configuration cakephp already ships
> database.php.default so that the user can copy it to his own
> database.php.  Should I do the same for core.php?  And what about the
> .htaccess files?
>
> thanks in advance
>         Lorenzo
>
> --
> Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
> HOME:http://www.lorenzobettini.itMUSIC:http://www.purplesucker.com
> BLOGS:http://tronprog.blogspot.com http://longlivemusic.blogspot.com