From: hickert Date: Tue, 19 Jun 2007 07:14:15 +0000 (+0000) Subject: removed old setup templates X-Git-Url: https://git.tokkee.org/?a=commitdiff_plain;h=44d930017c1f7ff8c0babb0fd16950ccfba4d9f8;p=gosa.git removed old setup templates git-svn-id: https://oss.gonicus.de/repositories/gosa/trunk@6624 594d385d-05f5-0310-b6e9-bd551577e9d8 --- diff --git a/ihtml/themes/default/setup.tpl b/ihtml/themes/default/setup.tpl deleted file mode 100644 index df4d2be7c..000000000 --- a/ihtml/themes/default/setup.tpl +++ /dev/null @@ -1,40 +0,0 @@ - -
- - - -{$errors} - - - - - - - - - -
- - - setup.php -
- - {include file="$content"} - -
- - - -
- - diff --git a/ihtml/themes/default/setup_finish.tpl b/ihtml/themes/default/setup_finish.tpl deleted file mode 100644 index ccd0b19bb..000000000 --- a/ihtml/themes/default/setup_finish.tpl +++ /dev/null @@ -1,32 +0,0 @@ -

{t}Setup finished{/t}

- -{t}Basically the setup is finished. You can check the result of the schema check here and download the autogenerated gosa.conf below.{/t} - -

 

- -

{t}Schema Configuration{/t}

-

{$schemas}

- -

 

- -

{t}Configuration File{/t}

-

- {t}GOsa setup has collected all data needed to create an initial configuration file. Save the the link below as your gosa.conf and place that file in /etc/gosa. Change it as needed.{/t} -

- - - -

- {t}After placing the file under /etc/gosa, place make sure that the webserver user is able to read gosa.conf, while other users shouldn't. You may want to execute these commands to achieve this requirement:{/t} -

- -
-# chown root.{$webgroup} /etc/gosa/gosa.conf
-# chmod 640 /etc/gosa/gosa.conf
-
- -

- - - -

diff --git a/ihtml/themes/default/setup_introduction.tpl b/ihtml/themes/default/setup_introduction.tpl deleted file mode 100644 index 451855b52..000000000 --- a/ihtml/themes/default/setup_introduction.tpl +++ /dev/null @@ -1,22 +0,0 @@ -

{t}Welcome to the GOsa setup!{/t}

- -

- {t}It looks like you're calling GOsa for the first time - no configuration was found. This setup like script will try to aid you in creating a working configuration by performing three major steps: first we'll check the PHP installation for required modules, than we're going to check for optional/needed programms and after you've provided basic information for your LDAP connectivity, we're going to check your LDAP setup.{/t} -

-

 

-
-{$tests} -
-

- - -

- -

 

-

- {t}You can also use the new and more-advanced way of inspecting your PHP-installation. It will give you information about the exact function that could not be found (functions that could be found are not mentioned). This is useful if you know what you're doing.{/t} -

- - diff --git a/ihtml/themes/default/setup_step2.tpl b/ihtml/themes/default/setup_step2.tpl deleted file mode 100644 index 763b3f1f5..000000000 --- a/ihtml/themes/default/setup_step2.tpl +++ /dev/null @@ -1,14 +0,0 @@ -

{t}Setup continued...{/t}

- -

- {t}Step two looks for a set of helper programms and checks if they have the correct minimum version.{/t} -

-

 

- -{$tests} - -

- - - -

diff --git a/ihtml/themes/default/setup_step3.tpl b/ihtml/themes/default/setup_step3.tpl deleted file mode 100644 index b87162ded..000000000 --- a/ihtml/themes/default/setup_step3.tpl +++ /dev/null @@ -1,19 +0,0 @@ -

{t}Setup continued...{/t}

- -

- {t}Now we're going include your LDAP server and create an initial configuration. After you've entered the server URI below, a quick check is performed if required LDAP schemas are in place. Samba versions are autodetected by the installed objectclasses. Details on how your LDAP tree is organized will be asked later on.{/t} -

- -

 

-
- -{t}Please enter the server URI to allow the setup to connect your LDAP server (Example: ldap://your.server:389).{/t} -
-
-URI  - -

- - - -

diff --git a/ihtml/themes/default/setup_step4.tpl b/ihtml/themes/default/setup_step4.tpl deleted file mode 100644 index e4b3e40b7..000000000 --- a/ihtml/themes/default/setup_step4.tpl +++ /dev/null @@ -1,116 +0,0 @@ -

{t}Setup continued...{/t}

-{t}The following fields allow the basic configuration of GOsa's behaviour and affect various properties in your main configuration.{/t} - -

 

- -

- {t}Enter a description for the location you're configuring here{/t}: -

- - - - - -
{t}Location name{/t}
- -

 

-

- {t}GOsa always acts as admin and manages access rights internally. This is a workaround till OpenLDAP's in directory ACI's are fully implemented. For this to work, we need the admin DN and the corresponding password.{/t} -

- - - - - - - - - - -
{t}Admin DN{/t}
{t}Admin password{/t}
-

 

- -

- {t}Some basic LDAP parameters are tunable and affect the locations where GOsa saves people and groups, including the way accounts get created. Check the values below if the fit your needs.{/t} -

- - - - - - - - - - - - - - - - - - - - - - -
{t}Base {/t}
{t}People storage ou{/t}
{t}People dn attribute{/t} - -
{t}Group storage ou{/t}
{t}ID base for users/groups{/t}
- -

 

- -

- {t}GOsa supports several encryption types for your passwords. Normally this is adjustable via user templates, but you can specify a default method to be used here, too.{/t} -

- - - - - -
{t}Encryption algorithm{/t} - -
- -

 

- -

- {t}GOsa has modular support for several mail methods. These methods provide interfaces to users mailboxes and general handling for quotas. You can choose the dummy plugin to leave all your mail settings untouched.{/t} -

- - - - - -
{t}Mail method{/t} - -
- -

 

- -

- {t}GOsa may cause PHP interpreter errors, particularly in case of Beta versions. In some cases it would be helpful to enable the error reporting.{/t} -

- - - - -
{t}Display PHP errors{/t} - -
-

- - - -

diff --git a/ihtml/themes/default/setup_useradmin.tpl b/ihtml/themes/default/setup_useradmin.tpl deleted file mode 100644 index bcbc82396..000000000 --- a/ihtml/themes/default/setup_useradmin.tpl +++ /dev/null @@ -1,43 +0,0 @@ - -{if $exists == TRUE} -

{t}You already have an Administrative Account and a Group.{/t}

-{else} - -

{t}You're missing an administrative account for GOsa, you'll not be able to administrate anything!{/t}

-{/if} - -

-{t}To provide full administrative access to GOsa, you need to create a special group which contains the administrative user. The setup program can assist you with this task. Enter the desired username and the password below to create the missing entries.{/t} -

- -

-   -

- -
- - - - - - - - - - -
- {t}Username{/t} - - -
- {t}Password{/t} - - -
-{$str_there} -

- - - -

-