Re: Application bootstrap.php

[davide]

AD7six wrote:
> ...
> Personally, I use the following (potentially flawed) upgrade approach
> backup app/config folder,
> replace the cake folder,
> replace the app/config folder
> replace the app/* folders
> overwrite the app/config folder with the backup (so that my version of
> the config files exist, but don´t miss any new files should there be
> any).

Ok, you make upgrade as I do. For me it's a must to backup every evening
and before any upgrade. :)

regards
Davide






signature.asc
Description: OpenPGP digital signature

Re: Application bootstrap.php

[AD7six]

Hi Davide,

Preamble:
The files inside the config folder define the config of your
application. Normally the contents of the app folder as a whole don´t
change with new version of cake - except between releases (e.g. meaning
that going from v 3100 to v 3101 would probably mean no changes to the
app/config folder at all). If a new feature is included in Cake, it is
possible that for example a new constant is defined in
app/config/core.php.

Personally, I use the following (potentially flawed) upgrade approach
backup app/config folder,
replace the cake folder,
replace the app/config folder
replace the app/* folders
overwrite the app/config folder with the backup (so that my version of
the config files exist, but don´t miss any new files should there be
any).

Then, if there are any funny errors:
compare the files in your app/config folder  to check nothing is
missing (such as the changes some weeks/months/eons ago to the database
and inflections files which introduced new parameters).

Regarding your query:
The bootstrap is just one of the files in the config folder, and I´m
guessing you only changed the database and bootstrap files within it.
The problem you describe would be compounded if you made changes to any
of the other files there and followed the upgrade process you mention.
In this case I think you would probably quickly change your approach to
stop redefining your changes to the core, inflections, bootstrap etc.
files ;)

However, and I am but one person with an optionion, I think what would
be useful is a page in the manual on how to upgrade (does it already
exist? I coudn't find it if so), as although it´s a pretty simple
process people do it in different ways and leaping a few hundred build
numbers can mean that an app stops working just because of missing
constants.

Other thoughts?

Cheers,

AD7six


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Cake 
PHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/cake-php
-~--~~~~--~~--~--~---

Application bootstrap.php

[davide]

Hello everybody.

Every time I upgrade to a new release, I also upgrade the cake files
inside my own apps by copying the empty "app" provided inside it and
make it rewrite all files.

Maybe this is not the best way to do this but it works pretty well for
everything (for me) except for the application bootstrap.php file. I use
this file for defining my own constants and requires (maybe even this is
not the right way to proceed) and when I overwrite with the empty app,
this file is overwritten.

Could it be possible to have the bootstrap.php behave like the
database.php? So cake is provided with the bootstrap.php.default and if
a user need it, he will copy the file as boostrap.php and then edit it.

Do you think I should open an enhancement ticket?

Thanks a lot
Davide



signature.asc
Description: OpenPGP digital signature