eZ Community » Forums » General » eZ Publish Check is out !
expandshrink

eZ Publish Check is out !

eZ Publish Check is out !

Monday 19 April 2010 12:24:32 pm - 4 replies

Hi everybody,

Pushing the "go live" button of a brand new project usually brings its load of stress and last-minute questions :

  • Did i remove all test content, including the pictures of my last week end on the coast ?
  • Did i enable view caching on all pages ?
  • Were all settings turned into production mode ?
  • Is the application ready to avoid the "But, it works on my machine" symptom ?

A series of points are to be checked systematically, every time a website is launched. Like others did on other technologies, the eZ Community needed an "eZ Publish-check" tool, helping at not overlooking the obvious, usual things.

Here it is, open to collaboration and containing a fair first amount of check-points :

The translation is in progress, as well as filling this list up. Should you want to contribute your experience back, drop an email at contact@ez-france.org

Cheers !

Modified on Monday 19 April 2010 12:29:34 pm by S├ębastien Morel

Monday 19 April 2010 12:52:29 pm

Nice and useful tool!

Monday 19 April 2010 12:57:06 pm

Should be turned into a script / extension!

Wednesday 05 May 2010 9:45:15 am

We have something like a script / check extension.

http://svn.projects.ez.no/ezadmin/trunk/extension/ezadmin/

we will add it to this extension in a couple of minutes...

the checks are extendable, plug-inable...

Wednesday 05 May 2010 11:34:49 am

@Bjorn: while I applaud your move, I think we could try to come up with something better:

- the ezadmin extension packages together lot of useful 'adminish' stuff

- there's a lot of overlap already between the ezadmin and ggsysinfo extensions. And maybe with some more

- I think for general-purpose extensions, it is better to focus on a specific aspect rather than try to include too many different functionalities

- on similar notes we already have extensions like ezgeshi, which can do syntax highlighting, ezcodesniffer to check for php coding style and ezdbintegrity, which will check for db integrity

In short: why not create a new extension, dedicated to implementing some "status check console"?

It can add both a gui and a lot of useful scripts to be run on the command line.

It will depend on the above mentioned extensions to provide core functionality avoiding duplication.

We can start building a list of things to be checked out, besides the ones already present in the op. Some of my pet peeves:

- php ini files missing the opening comment tag

- ini settings keys which are identical except for case (common error)

- whitespace in in settings (common error)

- check if definition of po classes match db structure

expandshrink

You must be logged in to post messages in this topic!

36 542 Users on board!

Forums menu