Configuring web services is as easy in OS X Mountain Lion Server (10.8) as it has ever been. To set up the default web portal, simply open the Server app, click on the Websites service and click on the ON button.
Only show instructions for your platform: Ubuntu Mac Windows. How to install the web application. On the server and can install all the dependencies, secure the. I'm a technology writer and web designer living in the UK. I write for a number of Apple-related sites, including Sparsebundle. I also create web templates available at ThemeForest and offer bespoke web design services at my own site, jordanmerrick.com. You can find me on both App.net and Twitter!
After a time, the service will start. Once running, click on the View Server Website link at the bottom of the pane. Provided the stock OS X Server page loads, you are ready to use OS X Server as a web server. Before we setup custom sites, there are a few things you should know. The first is, the server is no longer really designed to remove the default website. So if you remove the site, your server will exhibit inconsistent behavior.
Also, don’t remove the files that comprise the default site. Instead just add sites, which is covered next. Webmail is gone. You don’t have to spend a ton of time looking for it as it isn’t there. Also, Mountain Lion Server adds web apps, which we’ll briefly review later in this article as well. Finally, enabling PHP and Python on sites is done globally, so this setting applies to all sites hosted on the server.
Now that we’ve got that out of the way, let’s add our first custom site. Do so by clicking on the plus sign. At the New Web Site pane, you’ll be prompted for a number of options. The most important is the name of the site, with other options including the following:. Domain Name: The name the site is accessible from.
The default sites do not have this option as they are accessible from all names that resolve to the server. IP Address: The IP address the site listens on.
![For For](/uploads/1/2/5/4/125446383/645701901.png)
Any means the site is available from every IP address the server is configured to use. The default websites do not have this option as they are accessible from all addresses automatically. Port: By default, sites without SSL run on port 80 on all network interfaces, and sites with SSL run on port 443 on all network interfaces. Use the Port field to use custom ports (e.g., 8080). The default sites do not have this option as they are configured to use 80 and 443 for default and SSL-based communications respectively. SSL Certificate: Loads a list of SSL certificates installed using Keychain or the SSL Certificate option in the Settings pane of the Server application.
Store Site Files In: The directory that the files that comprise the website are stored in. These can be placed into the correct directory using file shares or copying using the Finder. Click on the drop-down menu and then select Other to browse to the directory files are stored in. Who Can Access: By default Anyone (all users, including unauthenticated guests) can access the contents of sites. Clicking on Anyone and then Customize brings up the “Restrict access to the following folders to a chosen group” screen, where you can choose web directories and then define groups of users who can access the contents. Additional Domains: Click on the Edit button to bring up a simple list of domain names the the site also responds for (e.g. In addition to krypted.com, add www.krypted.com).
Redirects: Click on the Edit button to bring up a list of redirects within the site. This allows configuring redirects to other sites. For example, use /en to load english.krypted.com or /cn to load china.krypted.com).
Aliases: Click on the Edit button to load a list of aliases. This allows configuring redirects to folders within the same server. For example, /en loads /Library/Server/Web/Data/Sites/Default. Index Files: Click on the Edit button to bring up a list of pages that are loaded when a page isn’t directly indicated.
For example, when visiting krypted.com, load the wp.php page by default. Advanced Options: The remaining options are available by clicking on the “Edit Advanced Settings” button. Enable Server Side Includes: Allows administrators to configure leveraging includes in web files, so that pieces of code can be used across multiple pages in sites. Allow overrides using.htaccess files: Using a.htaccess file allows administrators to define who is able to access a given directory, defining custom user names and passwords in the hidden.htaccess file. These aren’t usually required in an OS X Server web environment as local and directory-based accounts can be used for such operations. This setting enables using custom.htaccess files instead of relying on Apple’s stock web permissions. Allow folder listing: Enables folder listings on directories of a site that don’t have an Index File (described in the non-Advanced settings earlier).
Allow CGI execution: Enables CGI scripts for the domain being configured. Use custom error page: Allows administrators to define custom error pages, such as those annoying 404 error pages that load when a page can’t be found.
Make these web apps available on this website: A somewhat advanced setting, loads items into the webapps array, which can be viewed using the following command: sudo serveradmin settings web:definedWebApps Once you’ve configured all the appropriate options, click on Done to save your changes. The site should then load.
Sites are then listed in the list of Websites. The Apache service is most easily managed from the Server app, but there are too many options in Apache to really be able to put into a holistic graphical interface.
The easiest way to manage the Websites service in OS X Mountain Lion server is using the serveradmin command. Apache administrators from other platforms will be tempted to use the apachectl command to restart the Websites service. Instead, use the serveradmin command to do so. Hey, First of all, thanks for doing this – as a new OSX server user i was more than a little confused. I have one question – You mentioned under the site configuration descriptions that you can change “Who Can Access” by: “Clicking on Anyone and then Customize brings up the “Restrict access to the following folders to a chosen group” screen, where you can choose web directories and then define groups of users who can access the contents.” I don’t seem to be able to work out where “Customize” is I have set up a new user called “webuser” whom I want to give access to Thanks again! Hi Charles, you mentioned you enjoyed a challenge! I’m trying to do something under OS X server which is relatively painless to do on any Linux server, but the undocumented internals of OS X are stymying me.
My ML 10.8.1 Server is serving three FQDN’s for mail and websites -FQDN 1- ML wiki / device manager / webcal, FQDN 2- one cms + a crm in a subdomain and FQDN 3, a plain HTML info site. I have another internal machine / site that does snmp monitoring of the machines on the LAN as well as ups monitoring via NUT ( driver for the ups will not work under OS X either integrated Energy Settings Panel or under NUT USB driver.) I’d like to be able to access the snmp HTML server externally. It’s a trivial exercise to set a different port on the router and direct that to the snmp machine, or, if my main webserver was running Linux, to redirect via apache reverse proxy, but unfathomable in Mountain Lion apache setup via webapp. I’ve tried unsuccessfully to create a webapp plist to perform the proxy redirect to another internal LAN IP address:80 but it keeps breaking web sites within Server App.
I know you have a lot of free time ? so if you can maybe do an article on reverse proxy via webapp to another machine I’d be very happy! Keep up the great work. Thanks Charles I am sorry. No speak english. I have several domains registered goddady registered I need to host these domains on my server. your tutorial is OK but I have only one computer. I have only one internet connection.
I need to access each of these domains separately to install drupal and then, edit their Web-page content but only can access to Apple default site!!! What should I do to access each of my custom pages from the server itself Mountain Lion Server? One more time, I am sorry for my english. Thanks Charles.
I understand I can not access these domains locally from the same machine that contains the Mountain Lion Server? Can I edit the websites from a laptop inside this network conexion? If yes What should I write in the address bar of the browser to access each site and to edit?
Other solution I can give to each domain name that I add.” a different port”, for example: Apple default: 80 Adomain.com: 81 Adomain.com: 82 Adomain.com: 83 I then, also must open each of these ports on the router? Lot of love Charles Alex. Thanks Charles. If edit /etc/hosts file like this: 127.0.0.1.NO working!!!! ## # Host Database # # localhost is used to configure the loopback interface # when the system is booting. Do not change this entry. ## 127.0.0.1 localhost 255.255.255.255 broadcasthost::1 localhost fe80::1%lo0 localhost 127.0.0.1 127.0.0.1 127.0.0.1 127.0.0.1 butlike this 192.168.1.100.NO working!!!!
192.168.1.100 is the server internal IP. ## # Host Database # # localhost is used to configure the loopback interface # when the system is booting. Do not change this entry. ## 127.0.0.1 localhost 255.255.255.255 broadcasthost::1 localhost fe80::1%lo0 localhost 192.168.1.100 192.168.1.100 192.168.1.100 192.168.1.100 Es ok?