Steps to setting up VR for Web
Live demo website
I used A-Frame for front-end and AWS Lightsail for the server.
Create or locate A-Frame file you will want to use.
To use A-Frame on a new file, create a new index.html file, and attach this line to the head tag of the file:
This line adds a CDN for A-frame's implementation, which is a URL that hosts the necessary A-frame files on multiple servers across the globe, and for efficiency downloads the files from the one that is closest to you. <REVISION STAGE: look up how A-Frame explains their own CDN>
To add more features, look at the A-Frame documentation here. If you just want a basic VR environment then copy this text as your html file:
<a-box position="-1 0.5 -3" rotation="0 45 0" color="#4CC3D9"></a-box>
<a-sphere position="0 1.25 -5" radius="1.25" color="#EF2D5E"></a-sphere>
<a-cylinder position="1 0.75 -3" radius="0.5" height="1.5" color="#FFC65D"></a-cylinder>
<a-plane position="0 0 -4" rotation="-90 0 0" width="4" height="4" color="#7BC8A4"></a-plane>
The next step is to get a server. I used AWS Lightsail, since I will integrate dynamic multiplayer features later. But, if all you want is a static website for a VR interface, then there are lots of options, including Github Pages, Netlify, or Vercel). Github Pages is convenient because it can upload files directly from a GitHub Repo itself.
I bought a test domain on Google Domains, then transferred the DNS to AWS so that it was easier to work with my server.
Attach server to the domain using the Domain Name Service (DNS) of whatever server set-up you are using.
Setup the web server framework
A Web Server framework is a tool that allows you to host webpages when clients visit your IP address.
The most popular open-sourced web servers are NGINX and Apache. Of these, Apache is easiest to set-up. I used NGINX.
To install these on a linux-based server, use:
sudo apt-get nginx or sudo apt-get apache
Encrypt the server. Since VR can only be accessed through HTTPS, we must encrypt the server before accessing it from another device.
Next, you will want to obtain a certificate from a Certificate Authority so that clients can visit your website through TLS, a security framework. This ensures that data sent to and from the server is encrypted, so it is more difficult for intermediaries to access it.
A Certificate Authority verifies that the server you access corresponds to the domain name that you accessed it through.
Let's encrypt is a free service that makes it really difficult to obtain a certificate from a trusted CA. I would recommend using their Certbot if possible. If you are using AWS Lightsail through Bitnami, like I did, you cannot use certbot, and instead should follow their instructions for getting authorized listed–NGINX or Apache.
Optional: add redirecting of www, https if you don’t want to type it out fully
Try changing config file with server name as both www and example.com