EasyRTC: Using Alongside Other Servers
EasyRTC supports working alongside of Apache, IIS, and other web servers. In these cases, your web application would use EasyRTC to just handle signaling. All html and other files would continue to be hosted on the current web server.
- EasyRTC can be set to use a different port to avoid conflicts (such as 8080)
- In client code, you must tell EasyRTC the socket.io URL prior to running
- If the EasyRTC server is simply on a different port you can use:
- If your web server is running SSL, then EasyRTC should too
- Ensure that all client API files resolve properly from your HTML. If API's remain hosted on the EasyRTC server your HTML may need to explicitly link to them. Commonly linked to API files are:
- /easyrtc/easyrtc_ft.js (optional file transfer api)
Walkthrough for Simple Audio Video Demo
Here are some steps to running the simple audio video demo from your web server. This is assuming you are running locally with your web server on port 80, and EasyRTC on port 8080.
- Copy the EasyRTC /demos folder to your web root (or a sub folder)
- Replace all instances of
- Insert the following to be the first line within the connect() function:
- Start your webserver and EasyRTC server
- In your browser visit:
Your own WebRTC app can then be developed in a similar fashion.
If You Run Into Problems
Please feel free to post on our discussion forum: