On 7/18/2018 12:49 PM, Robert Watterson wrote:

If I manage ldap entries and dirsrv server options via command line only, do I even need an admin server component?

No.

I've been using Apache Directory Studio for my non-command line needs on a single 389 instance, seems to work out OK so far. The admin server (o=netscape) is installed and running, but I haven't been using the GUI.  I'm about to spin up two new servers and do multi-master replication and certificates/TLS.

On a production server where all content changes are done via scripts (no GUI needed) do I even need to spin up an admin server?

We won't be using Admin Express, DS Gateway, Org Chart, etc. We'll never be managing more than 3-4 production ldap servers.

Am I missing something critical by installing just the actual 389 servers and NOT the admin instance?

Admin Server is really an http server that invokes CGI programs to do things that are not doable via LDAP (e.g. start and stop the LDAP server).

You can do all those things from the command line by logging into the machine the server is running on.

On Wed, 2018-07-18 at 14:49 -0400, Robert Watterson wrote:

Hi forgive the newbie question, but I've searched the 389-users archive and didn't see an answer.....

If I manage ldap entries and dirsrv server options via command line only, do I even need an admin server component? I've been using Apache Directory Studio for my non-command line needs on a single 389 instance, seems to work out OK so far. The admin server (o=netscape) is installed and running, but I haven't been using the GUI. I'm about to spin up two new servers and do multi- master replication and certificates/TLS. On a production server where all content changes are done via scripts (no GUI needed) do I even need to spin up an admin server? We won't be using Admin Express, DS Gateway, Org Chart, etc. We'll never be managing more than 3-4 production ldap servers. Am I missing something critical by installing just the actual 389 servers and NOT the admin instance?

Hi there,

In supplement to Mark's comments, not only are we pusing a new admin in the form of cockpit, we also want to improve the CLI to be a first glass admin interface. We have a suite of new tools coming (dsctl, dsconf and dsidm) that will absorb all the existing perl, and make many routine tasks for the CLI significantly easier to achieve.

I hope that we can make the CLI the only point of contact for you in the future, and would love to hear your feedback on it if you try it out.

Thanks!

---

389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject....