Ticket #161 (new new feature)

Opened 1 year ago

Last modified 4 days ago

Possibility to put an application offline

Reported by: laurentj Assigned to: laurentj
Priority: normal Milestone: Jelix 1.2
Component: jelix:core Version: 1.0 beta2
Severity: minor Keywords: update offline
Cc: Php version:
Review: Hosting Provider:
Documentation needed: 0 Blocking: 31

Description (Last modified by laurentj)

Jelix should contains a way to put offline temporarily an application (for maintenance for instance).

An example of implementation : Jelix could check the existance of a OFFLINE file in var/config. If this file exists, it displays an html page (the name of this html file could be set in a config parameter) insead of executing an action. Of course, some specific http headers should be sent (HTTP/1.1 503 Service Unavailable).

This system should be used by the update/install system.

Change History

04/18/07 11:40:30 changed by laurentj

  • description changed.

05/16/07 21:33:26 changed by bballizlife

This concept is quite simple to use by developers as it allows to simply upload a file via FTP, but what about the performances of checking the existence of such a file at every request ?

Couldn't we add an option in the application configuration that would be less hangry and still easy to use ? For example : applicationOffline = true

05/18/07 09:54:36 changed by laurentj

why not. There is an other case of use : we can imagine a CMS backend where the user can put its application (frontoffice) offline. In this case, it is easier to create or delete a file than modifying an ini file.

But you're right : performance are bad when testing a file..

08/06/07 20:41:28 changed by laurentj

  • milestone changed from Jelix 1.0beta3 to Jelix 1.0.

09/05/07 12:13:47 changed by laurentj

  • milestone changed from Jelix 1.0 to Jelix 1.1.

09/05/07 12:30:32 changed by laurentj

  • priority changed from high to normal.

12/04/07 22:52:24 changed by laurentj

  • blocking deleted.

12/04/07 22:53:09 changed by laurentj

  • blocking set to 31.

12/17/07 16:23:36 changed by laurentj

  • blocking deleted.

12/17/07 16:24:50 changed by laurentj

  • blocking set to 31.

04/24/08 01:23:29 changed by laurentj

  • review changed.
  • docneeded changed.
  • milestone changed from Jelix 1.1 beta 1 to Jelix 1.0beta2.

04/24/08 01:27:59 changed by laurentj

  • milestone changed from Jelix 1.0beta2 to Jelix 1.1 beta 2.

07/02/08 10:22:24 changed by bballizlife

I realize that in production mode, we do not force compilation and checkCacheFiletime is set to off. So configuration files are not compiled again, except if we clear the cache of the application.

This means that updating the configuration file to set, for example, applicationOffline = true would not work, unless we clear the cache. But as being in maintenance mode often means updating the application, this may not be a real problem.

I carry on thinking at a nice way to implement such a feature...

08/26/08 00:36:15 changed by laurentj

  • milestone changed from Jelix 1.1 beta 2 to Jelix 1.2.
Download in other formats: Comma-delimited Text Tab-delimited Text RSS Feed