Message-ID: <952911623.4402.1485866390833.JavaMail.confluence@ip-10-127-227-164> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_4401_2118120966.1485866390833" ------=_Part_4401_2118120966.1485866390833 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html Removing eZ Publish

Removing eZ Publish

This section describes how to completely remove an eZ Publish in= stallation from a system.

Removing eZ Publish is done in four steps:

  1. Deleting the eZ Publish directory
  2. Removing the database
  3. Reconfiguring Apache (optional)
  4. Removing the cronjobs (optional)
  5. Removing the NFS shares and cluster database (for clustered installatio= ns only)

WARNING! By following these steps, you will remove both eZ Publish and a= ll the data/content that you have put into the system. Everything will be l= ost, unless there are backups available somewhere.

Deleting the eZ = Publish directory

Remove the eZ Publish directory using your favorite tool.

Linux/UNIX

On Linux/UNIX systems, the removal would most likely be carried out usin= g the "rm" command:

=20
$ rm -Rf /path/to/ez_publish
=20

 

Please note that some file/directory permissions might be messed up. If = this is the case, it will prevent a regular user from removing all eZ Publi= sh files. You'll probably have to gain root access to solve this problem.

Windows

Windows users may simply delete the eZ Publish directory using the "Expl= orer".

Removing the database

MySQL

  1. Start the MySQL client, log in using your username and password:

    =20
    $ mysql -u <username> -p
    =20

     

    If the username/password is correct, the client will then present a "mys= ql>" prompt.

  2. Delete/remove the database using the drop command followed by the name o= f the database used by eZ Publish:

    =20
    mysql> drop database <database-name>;
    =20

PostgreSQL

  1. Remove the database by executing the PostgreSQL dropdb command from shel= l:

    =20
    $ dropdb <database-name>
    =20

Reconfiguring Ap= ache (optional)

If a virtual host setup was used, it is likely that the Apache configura= tion files contain eZ Publish specific settings. These settings will not be= needed anymore and thus they can be removed. Open the "httpd.conf" file using a text editor, scroll down to the bottom and remove the eZ= Publish specific virtual host settings. Remember to restart Apache after a= ltering the configuration file.

Removing the cro= njobs (optional)

If cron was configured to run eZ Publish specific jobs, then these will = have to be removed. You may have to edit a global cron file (under "/= etc/cron*") or use the "crontab" command with the -e (edit) parameter to edit a user's private cron file. Remove the = eZ Publish specific entries.

Windows users should remove any eZ Publish specific tasks from the speci= fic scheduling system they used, e.g. "windows scheduled tasks" (note that = eZ Publish does not install any scheduled task automatically on its own)

------=_Part_4401_2118120966.1485866390833--