There are a couple of parts to this article. The first is to describe the server command, stored in /Applications/Server.app/Contents/ServerRoot/usr/sbin/server. The description of the command by Brad Chapman was so eloquently put on this JAMF Nation post that I’m just gonna’ paste it in here:
So … I just installed Server 5.0.x tonight on my Mac Mini running Yosemite (10.10.5). There was a question that came up during JNUC about upgrading Server and having a way to accept the license agreement without going through the GUI.
So for shits and giggles I tried:
server setupIt’s not documented. And lo and behold, I got the prompt to accept the license agreement just like you do with Xcode.
Post your trip reports here! Can this be automated?
tardis:~ chapman$ sudo server setup Password: To use server, you must agree to the terms of the software license agreement. Press Return to view the software license agreement. ---insert license agreement here--- Do you agree to the terms of the software license agreement? (y/N) y Administrator access is required to set up OS X Server on this Mac. Type an administrator's user name and password to allow this. User name: chapman Password: Initializing setup... Getting server state... Getting host names... Writing server settings... Configuring Service Authentication... Creating certificates... Getting certificates... Renewing certificate... Enabling server password hashes for local users... Creating service principals... Initializing certificates... Preparing services... Preparing Caching service... Preparing Calendar service... Preparing Profile Manager service... Preparing File Sharing service... Preparing Software Update service... Preparing Messages service... Preparing Mail service... Preparing Web service... Preparing Calendar service... Preparing Wiki service... Preparing Calendar service... Preparing Profile Manager service... Initializing Wiki... Initializing Mail... Initializing VPN... Initializing Xcode... Enabling autobuddy for local accounts... Updating admin password policy... Checking DNS Configuration... Reading DNS configuration... Completing setup... server encountered errors during setup: Unknown error tardis:~ chapman$I don’t know what the ‘unknown error’ was.
The error is pretty much typical. I rarely see a server that doesn’t spawn some kind of error, and most errors will throw this. Oh well. The only option that he didn’t mention that isn’t meant for internal use is help, which doesn’t even indicate setup as a verb. Now, here’s where it gets fun. This is cute, but if you’re scripting a full server setup, you’ll want to bust out a little expect script here. I’m gonna’ put the username and password in cleartext here, to keep the script readable:
#!/usr/bin/expect
set timeout 300
spawn server setup
expect "Press Return to view the software license agreement." { send \r }
expect "Do you agree to the terms of the software license agreement? (y/N)" { send "y\r" }
expect "User name:" { send "MYADMINUSERNAME\r" }
expect "Password:" { send "MYPASSWORD\r" }
interact
Obviously, you would replace MYADMINUSERNAME with your admin username and MYPASSWORD with your password. But basically, drop the Server.app on a machine, run this, and you’re good to go. Now, hypothetically, if you’re spinning up a Caching server (e.g. if you’re building out 100 caching servers, this might come in handy), then you could use the commands described in this article I wrote earlier.
