[cvs] [Wiki] changed: Doc/Admin
Michael Rubinsky
mrubinsk at horde.org
Fri Aug 14 17:55:06 UTC 2009
mrubinsk Fri, 14 Aug 2009 13:55:06 -0400
Modified page: http://wiki.horde.org/Doc/Admin
New Revision: 1.6
Change log: typo
@@ -26,9 +26,9 @@
* You can go back to the main configuration screen with the
application list, where you will find some new elements at the bottom
of the screen. These elements apply to **all** generated
configurations **at once**. This means that you can continue to
configure the applications, and the save all generated configuration
files in one row.
* If you have FTP access to the web server, you can enter a valid
FTP user name and password, that has write permissions on the
{{conf.php}}, in the small form at the lower right. Click the upload
button and the generated PHP file will be uploaded with FTP.
* In the lower left there is a link to review the changes you've
made to all configuration files so far.
* Another link downloads an executable PHP script that can be run
on the server to save the generated configuration in the {{conf.php}}
files. Again: the file that you download here is **not** the generated
configuration, but a small PHP program that saves the generated
configuration on the file system. It has to be executed in a
shell/console. There is also:
- * A third link that saves this PHP script in the temporary
directory of the server. This is helpful so that you don't have to
first download the script locally, only to transfer it back to the
server in a 2nd stop. If executed, this script also tries to delete
itself, so that it's not left in the temporary folder, it might
contain passwords or other sensitive information. If the deletion
doesn't succeed, an error message is displayed. If you reload the
configuration interface after a failed deletion, you will see a new
link at the bottom that allows you to delete that script.
+ * A third link that saves this PHP script in the temporary
directory of the server. This is helpful so that you don't have to
first download the script locally, only to transfer it back to the
server in a 2nd step. If executed, this script also tries to delete
itself, so that it's not left in the temporary folder, it might
contain passwords or other sensitive information. If the deletion
doesn't succeed, an error message is displayed. If you reload the
configuration interface after a failed deletion, you will see a new
link at the bottom that allows you to delete that script.
All methods to store the configuration try to create a backup of the
old configuration. This only succeeds if there are sufficient file and
directory permissions. The new configuration will be stored anyway,
whether the backup could be created or not. You can restore a backup
from the individual application's configuration form. If a
configuration backup is found for that application, there will be
another button at the bottom for restoring the backup.
The different available configuration settings are further explained
on individual pages for the applications. Not all configuration
settings are explained, because some are self-explanatory or already
have sufficient explanations in the configuration interface, or
because they simply haven't been documented yet.
More information about the cvs
mailing list