You will then need to edit the config file
(config/letsencrypt_plugin.yml) and insert your administration
email address and your domain where they're marked.

At this point you'll need to have a server running for the Let's
Encrypt plugin to send and receive data from, so start a normal HTTP server
using `rails s -p 80` (see Start the Server, below, for more info on that
command).

Run the Rake task to get SSL certificates:

rake letsencrypt_plugin

You can now kill the HTTP server if you wish to.

Start the Server

To start the server, use

rails s -p 80

If you're on a machine that has multiple public-facing IPs, you'll
need to specify which one to bind to using the -b switch: on
Amazon EC2, I need to use rails s -p 80 -b 172.31.33.173 to get it
to run successfully.

Troubleshooting

If any of the above commands don't work, try using them under
sudo (or, if your Ruby installation uses RVM, you can try
rvmsudo). Beware of doing this with the Let's Encrypt plugin
commands - if you do this, you will also need to run the application server
under sudo or rvmsudo.

Beware of firewalls: if your server has a firewall that defaults to
'everything closed' mode, you will need to open some ports in it to
be able to run across the public Internet. On Amazon EC2 this is the case -
the security group governs the incoming and outgoing connections rules.
You'll need to open whichever port you're running on - if
that's normal HTTP, you want 80; if it's HTTPS you need 443.

Most site settings are configurable through the admin interface or through
privilege thresholds.