Configuration

Configuration#

Connect to SMTP server#

To allow Allegra to send e-mails (e.g. if you forgot your password) you should give Allegra access to an SMTP server. For testing purposes you could use your own e-mail account but this is not recommended if your SMTP server requires authentication. It is definitely best to create a dedicated email account for your Allegra installation.

Attention

You can send a maximum of 100 emails per day from Amazon Web Services servers. If you want to send more, you need to request it from AWS.

Nginx Proxy#

It is recommended to run the servlet container (Tomcat) behind an existing web server like Nginx. The web server forwards corresponding requests to the servlet container.

This way, the servlet container does not need to be secured with its own certificates and can run on any non-standard port.

Here is an example configuration for an Nginx proxy server:

location /allegra {
    # switch off logging
    access_log off;

    # redirect all HTTP traffic to localhost:9988/allegra
    proxy_pass http://localhost:9026/allegra;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header Host $host;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

    # WebSocket support (nginx 1.4)
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
}

Apache Proxy#

It is recommended to run the servlet container (Tomcat) behind an already existing web server like Apache. The web server forwards corresponding requests to the servlet container.

This way, the servlet container does not need to be secured with its own certificates and can run on any non-standard port.

Here is an example configuration for an Apache2 web server:

ProxyPass /allegra http://127.0.0.1:9026/allegra
ProxyPassReverse /allegra/ https://www.yourdomain.com/allegra/
ProxyPass /allegra ws://127.0.0.1:9026/allegra
ProxyPassReverse /allegra/ ws://www.yourdomain.com/allegra/
Contents