Postinstall
This page describes some things you can configure once you have completed the Bootstrap process.
If you are running the webapp using a cloud hosting service
such as EC2, then in the bootstrap process you might have used
a hostname that was provided by the hosting service.
For example, an Amazon EC2 server might have a hostname like
ec2-107-22-92-250.compute-1.amazonaws.com.
You can make CloudCoder available under a more meaningful hostname by setting up a DNS record for the webapp server. There are a couple ways that you can do this.
#. You can ask your IT department to add a DNS entry.
You will just need to give them the IP address of your webapp server.
#. You can purchase a domain name, and configure the DNS entry
yourself. Generally, the domain name registrars have a web
interface that makes it fairly easy to add DNS entries once you
have purchased a domain. Either a CNAME or A record will
work. Use an A record to associate a DNS name with your
webapp server's IP address, or a CNAME record to define
a DNS name as an alias for another DNS name (such as the one
provided by your hosting service.)
The Bootstrap process creates a self-signed (untrusted) SSL certificate, meaning that web browsers will issue a security warning when connecting to the webapp. Self-signed certificates are not insecure as such - data transferred between CloudCoder and the user's web browser will still be encrypted - but the security warning is annoying. You can fix this by installing a "real" SSL certificate.
The most complicated part of installing the SSL certificate is obtaining the SSL certificate: this involves purchasing the certificate from a trusted authority, which in turn requires you to prove that you are the legitimate owner of the domain name for which the certificate is issued.
