Currently Being ModeratedOct 21, 2012 11:25 AM (in response to ikevinjp)
Try using this info, its for Rumpus (who make a 3rd party FTP server) but the same method can be used to make any virtual host, so you can have more than one service running on the same port (or appear to run on the same port)
OS X Server Users:
OS X Server uses the Apache Web service, but uses special configuration files in the process. Changing the Apache config files directly may have inconsistent results. Try creating a virtual server in OS X Server, and then modifying the OS X Server config file for that virtual domain.
For example, to set up an alternate service using the "rumpus.acme.com" domain name, you would create a Web site in OS X Server called "rumpus.acme.com". Once you have done that, look in the folder:
There you will find a file that includes the alternate domain name, like "0000_any_80_rumpus.acme.com.conf". In that file is a VirtualHost configuration block which can be modified to include the proxy directives shown above. Some of OS X Server's configuration options, like the "IfModule" and "Directory" blocks, can be removed, since the virtual server won't actually be processing files from the file system. Other config options, like ServerName and ServerAdmin, can be left as specified by OS X Server.
Here is an example:
<VirtualHost *:80> ServerName rumpus.acme.com ServerAdmin firstname.lastname@example.org DocumentRoot "/Users/Shared" DirectoryIndex index.html index.php /wiki/ default.html CustomLog /var/log/apache2/access_log combinedvhost ErrorLog /var/log/apache2/error_log ProxyRequests Off <Proxy *> Order deny,allow Allow from all </Proxy> ProxyPass / http://rumpus.acme.com:8000/ ProxyPassReverse / http://rumpus.acme.com:8000/ </VirtualHost>
Remember to stop and start the Apache service (using OS X Server if you have customized the OS X Server config file) after making changes to force Apache to reload changes.
Currently Being ModeratedDec 28, 2012 1:40 PM (in response to ikevinjp)
I can answer one part of your question based on trial-and-error experiments (it's the error part I don't like
The priority for local page versus wiki is set using the "index files" option in Server App for your default web hosting sites.
You drag and drop the order of priorities. By default (on my site), when the http://mysite.com/ was used, it would look for the following in order:
/wiki/ (which apparently runs its own server)
So, if you want the wiki to be the default, then drag it to the first place in the list.
As for your other questions, not sure....
Currently Being ModeratedJan 5, 2014 5:26 AM (in response to Punctual Diva)
I've been messing with this for a while and your reply has been the fix.
As soon as I turned on the Wiki service, i lost all access to my other virtual hosts. It was fixed by removing the /wiki/ from the priority list!