-
Notifications
You must be signed in to change notification settings - Fork 105
Configuration apejsf
It's time to setup APE JavaScript Framework and check your APE server is working.
Put all APE JSF file in the virtualhost you just created in APE Server Configuration Apache.
Then, open the file Demos/config.js. Configure it as follows:
// To test, go to http://yourdomain.com/APE_JSF/Tools/Check/
APE.Config.baseUrl = 'http://yourdomain.com/APE_JSF'; //APE JSF
APE.Config.domain = 'yourdomain.com'; //Your domain, must be same as domain in aped.conf
APE.Config.server = 'ape.yourdomain.com:443'; //APE server URL
Note that "yourdomain.com" is used without a "www" subdomain, specifically not "www.yourdomain.com", in these entries. If you use APE on your local machine, replace "yourdomain.com" with "ape-test.local", like:
// To test, go to http://ape-test.local/APE_JSF/Tools/Check/
APE.Config.baseUrl = 'http://ape-test.local/APE_JSF'; //APE JSF
APE.Config.domain = 'ape-test.local'; // /etc/hosts domain, must be same as domain in aped.conf
APE.Config.server = 'ape.ape-test.local:443'; //APE server URL
Note the subdomain "ape" being located under the domain "ape-test.local" under the APE.Config.server entry.
The default port installed in the RPM installation is port 6969, and the APE JavaScript Framework separate download is packed as ape-jsf, so the following code may be more worthwhile:
// To test, go to http://ape-test.local/ape-jsf/Tools/Check/
APE.Config.baseUrl = 'http://ape-test.local/ape-jsf'; //APE JSF
APE.Config.domain = 'ape-test.local'; // /etc/hosts domain, must be same as domain in aped.conf
APE.Config.server = 'ape.ape-test.local:6969'; //APE server URL
This is a good example of how you may need to tweak your installation to get it to work how you want it to. Note that 6969 is just used in case the user starting the server is not root. If installed as a service implicitly run by root, then port 443 is a much better port to put it on. To do this, simply replace all occurrences of 6969 with 443 and ensure nothing is already running on port 443, then restart the aped daemon.
You can proceed to the next step: Run aped.