Difference between pages "Package:389 Directory Server" and "Translations:Install/Profiles/17/en"

(Difference between pages)
(Created page with "{{Ebuild |Summary=This is the core part of 389 Directory Server -- technically, all you need for an LDAP deployment, although many will want to install 389-ds-admin for the gr...")
 
(Importing a new version from external source)
 
Line 1: Line 1:
{{Ebuild
+
To add a mix-in:
|Summary=This is the core part of 389 Directory Server -- technically, all you need for an LDAP deployment, although many will want to install 389-ds-admin for the graphical management capabilities, too.
+
|CatPkg=net-nds/389-ds-base
+
|Maintainer=Psychopatch,
+
|Repository=Funtoo LDAP Overlay
+
}}
+
This is the core part of 389 Directory Server -- technically, all you need for an LDAP deployment, although many will want to install 389-ds-admin for the graphical management capabilities, too.
+
 
+
After emerge, to set up your LDAP server, run:
+
 
+
<console>
+
# ##i##setup-ds.pl
+
</console>
+
 
+
If you want the Apache-based graphical admin console set up, along with your LDAP server, <tt>emerge 389-ds-admin</tt> and run:
+
 
+
<console>
+
# ##i##setup-ds-admin.pl
+
</console>
+
 
+
This will set up both for you, and then you will be able to remotely manage your LDAP server using the Java-based [[Package:389 Directory Server Console]].
+
{{EbuildFooter}}
+

Latest revision as of 04:31, July 14, 2015

To add a mix-in: