Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Clone this wiki locally
To work APE need a special DNS configuration, but the simple configuration work with an special domain "local.ape-project.org" that point to 127.0.0.1. If you want to install APE on your local computer without configure DNS and save you some time use this configuration. If you use this configuration, you must use http://local.ape-project.org to access to all your application using APE.
In order to use APE features like multi-tabbing or windowing your domain name must be specially configured. Whether you're setting APE up as a server or configuring for local access consult the correct section below for details on what needs to be done.
If you use APE on a server
You need to:
- Create a subdomain pointing to the server where APE is installed. For example, the subdomain of yourdomain.com is ape.yourdomain.com
- Create a Catch-All CNAME redirecting all requests from *.ape.yourdomain.com to ape.yourdomain.com
Edit your DNS configuration.
If you use bind9 add those line to your zone file:
ape IN A x.x.x.x ; The IP address of your APE server *.ape IN CNAME ape
If you use dnsmasq add those line to your /etc/dnsmasq.conf file:
address=/ape.ape-test.local/x.x.x.x #x.x.x.x ; The IP address of your APE server
If you use APE on your local computer
Edit your /etc/host file and add the following lines...
127.0.0.1 ape-test.local 127.0.0.1 ape.ape-test.local 127.0.0.1 0.ape.ape-test.local 127.0.0.1 1.ape.ape-test.local 127.0.0.1 2.ape.ape-test.local 127.0.0.1 3.ape.ape-test.local 127.0.0.1 4.ape.ape-test.local 127.0.0.1 5.ape.ape-test.local 127.0.0.1 6.ape.ape-test.local 127.0.0.1 7.ape.ape-test.local 127.0.0.1 8.ape.ape-test.local 127.0.0.1 9.ape.ape-test.local
If you are running APE on Windows in a virtual machine
If you are running APE on Windows in a virtual machine, edit the file
To access across two LAN-connected computers this same method of setting the hosts file entries correctly works without needing to set the DNS entries. This results in a locally accessible server which is not visible from outside but is visible inside but acts just as though it would if it were accessed remotely. This is ideal for tests which require controlled access.
To do this, edit the server hosts file in the same way as above. On any viewing LAN computer, add the following lines onto their own hosts file...
(Assuming the server's internal IP were 192.168.1.100) /etc/hosts:
192.168.1.100 ape-test.local 192.168.1.100 ape.ape-test.local 192.168.1.100 0.ape.ape-test.local 192.168.1.100 1.ape.ape-test.local 192.168.1.100 2.ape.ape-test.local 192.168.1.100 3.ape.ape-test.local 192.168.1.100 4.ape.ape-test.local 192.168.1.100 5.ape.ape-test.local 192.168.1.100 6.ape.ape-test.local 192.168.1.100 7.ape.ape-test.local 192.168.1.100 8.ape.ape-test.local 192.168.1.100 9.ape.ape-test.local
This makes it so the same URL may be entered to test locally on the server, or on any networked computer so configured.
Again, this works for Windows machines viewing a Linux server. Just edit the Windows hosts file - again, located at
C:\WINDOWS\system32\drivers\etc\hosts - as stated above on the viewing computer.
Do not use localhost for your domain or any domain without TLD or your APE installation will not work!
Run your APE Server
You can proceed to the next step: Configuration apejsf