he devs, i found a big bad issue in sf1.4...we use the check_lock setting for setting the plattform into maintenance mode (PROD env). The problem is, if the application is locked in the PROD env, i am unable for example "clear the prod cache", running some maintenance tasks on the application (some need the application configured in PROD env)...or whatever instanciates the application in PROD mode (the cache clear task does that)
Thats totally bad! Think of this deployment lifecycle example: * lock the remote prod application * sync the project sources * do some important tasks on the remote server * release the remote lock I think we should implemented an "ignore locking if the application was not instanciated by the webserver", every call from the cli shouldnt respect the lock even on the PROD env. I dont think the core devs are willing to change this behavior in sf1.4, but maybe someone has a clue how can i achive this (maybe without overriding the sfApplicationConfiguration class) in my own project. Thanks Robert -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
