Skip to content
GOsa core
PHP Perl Smarty JavaScript Roff CSS Other
Branch: master
Clone or download
master-caster Merge pull request #31 from FabianHenneke/fhenneke_unserialize
Fix the decoding of filter settings cookie
Latest commit f1f7ad0 Aug 19, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
bin (see #13) using the correct encryption method Apr 4, 2018
contrib Merge pull request #24 from sunweaver/pr/autocompletion-config-option Aug 23, 2018
doc Removed obsolete png.js Aug 8, 2010
html Fix the decoding of filter settings cookie Aug 16, 2019
ihtml/themes/default Translated some text. Apr 20, 2011
include Merge pull request #24 from sunweaver/pr/autocompletion-config-option Aug 23, 2018
locale/core Remove warning that is not valid anymore. Nov 16, 2015
plugins Merge pull request #23 from sunweaver/pr/disable-password-field-when-… Aug 27, 2018
redhat refs #12 Feb 23, 2018
setup switch from mysql to mysqli Nov 28, 2017
AUTHORS Updated Authors text Aug 30, 2010
CODING Added CODING guidelines - these have to be fixed in GOsa ;-) Aug 6, 2008
COPYING Fixed license address Aug 16, 2011
Changelog Updated changelog Jul 25, 2012
FAQ Fix FAQ entry for membership-in-more-than-16-groups-when-on-NFS. Nov 16, 2015
INSTALL Updated INSTALL file Oct 7, 2009
README.ldap Renamed files and updated compression rules Apr 12, 2011
README.md
README.safemode Starting move Dec 12, 2007
dh-make-gosa Reverted accidently removed files Apr 11, 2011
dh-make-gosa.1 apply typo fixes from debian_edu patch Nov 28, 2017
gosa-encrypt-passwords.1 - updated manpages for copyright years Sep 17, 2009
gosa-encrypt-passwords.pod - updated manpages for copyright years Sep 17, 2009
update-gosa Removed help generation Dec 6, 2010
update-gosa.1 - updated manpages for copyright years Sep 17, 2009
update-gosa.pod - updated manpages for copyright years Sep 17, 2009
update-locale allow {t} to be translated that contain parameters Nov 28, 2017
update-locale.1 - updated manpages for copyright years Sep 17, 2009
update-locale.pod - updated manpages for copyright years Sep 17, 2009
update-online-help.1 - updated manpages for copyright years Sep 17, 2009
update-online-help.pod - updated manpages for copyright years Sep 17, 2009
update-pdf-help Changed to apply to core/plugins split. Mar 14, 2008
update-pdf-help.1 - updated manpages for copyright years Sep 17, 2009
update-pdf-help.pod - updated manpages for copyright years Sep 17, 2009

README.md

GOsa 2.7 README

Information

GOsa is an LDAP administration frontend for user administration. It is NO GENERIC frontend to dictionary servers. Information is stored in the way the underlying concepts suppose them to be stored (i.e. people accounts are stored in "ou=people" subtrees, etc.) This can only be configured marginally.

Complete setups applying Kerberos, AFS, LDAP, Mail, Proxy and Fax setups are not trivial at all. You should be familiar with these components and with your UNIX installation, of course. This file is (and will not be) an introduction to any of these components. See INSTALL for a quick overview about what to do, to get the things up and running.

If you want to try out GOsa on an easy-to-install server, we recommend playing with a Debian Edu mainserver installation. The Debian Edu mainserver has GOsa pre-installed and set up out-of-the box.

Translations

GOsa is not available in your native language? Just read on...

Translations (or i18n) in GOsa are done by the gettext library. As a result, every set of translations is stored inside one directory per language as a text file called messages.po.

For GOsa, you've to differenciate between gosa-core and the various gosa-plugins. The core has its translation and every plugin has a seperate translation of its own, too.

GOsa core can be translated by taking a look at the locales/core directory. Just take the messages.po file and copy it to some other location and put your translations into the msgstr fields of this file. For more comfort, use programs like i.e. poedit to achieve this. You may look at the de/LC_MESSAGES for the way how it works.

If you're done with that, create a directory for your language using the ISO shortcuts (i.e. es for spain) with a subdirectory LC_MESSAGES. For, e.g., the Spanish translation this would be:

 gosa-core/locales/core/es/LC_MESSAGES

Put the freshly translated Spanish messages.po into this directory.

To test this, you've to deploy the messages.po file in your running copy of GOsa and run the update-gosa command, to let GOsa merge the translations. Then, make sure your Apache web server has locale support or, in case of Debian, that the specific locale will be generated (via dpkg-reconfigure locales).

For gosa-plugins, every plugin has a locales directory. Translation works like described for gosa-core.

Always run update-gosa after you've added translations in order to let GOsa compile and re-sync the translations.

Contribute Translations

You may want your translations to be included in the main GOsa repository, then just file and issue for the correct GOsa component and attach the .po there.

Notes

Be sure that gosaUserTemplates are not able to log into your server, since they may have no password set. Example configs can be found in the contrib directory.

Have fun!


Cajus Pollmeier pollmeier@gonicus.de

You can’t perform that action at this time.