Question

What's the best way to handle the scaffold when it comes to the deployment stage?

Leave it there? But then what's the best way to protect the access of it?

Remove it? But then I need another system to access all the data, right?

How do people usually handle the scaffold in CakePHP which is very useful in the building process?

Was it helpful?

Solution

Most people would not use scaffold anymore when getting close to deployment. That is where "bake" comes into play.

You usually only scaffold while still changing the database structure heavily. As soon as it gets stable you use custom bake templates to bake your views to real files. I actually never use scaffolding as bake has way more advantages (such as full customization of the template output. And rebaking is not that big of a deal. It is pretty fast to achieve.

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top