-```
- - replace:
- filename: /var/www/discourse/config/environments/production.rb
- from: /end/
- direction: reverse
- to: |
- config.action_mailer.delivery_method = :smtp
- config.action_mailer.smtp_settings = {
- :address => 'smtp.mandrillapp.com',
- :port => 587,
- :domain => 'mydomain.com',
- :user_name => 'user@example.com',
- :password => 'some_password',
- :authentication => 'login',
- :enable_starttls_auto => true
- }
- end
+If you want a multiple container setup, see the `data.yml` and `web_only.yml` templates in the samples directory. To ease this process, `launcher` will inject an env var called `DISCOURSE_HOST_IP` which will be available inside the image.
+
+WARNING: In a multiple container configuration, *make sure* you setup iptables or some other firewall to protect various ports (for postgres/redis).
+On Ubuntu, install the `ufw` or `iptables-persistent` package to manage firewall rules.
+
+### Email
+
+For a Discourse instance to function properly Email must be set up. Use the `SMTP_URL` env var to set your SMTP address, see sample templates for an example. The Docker image does not contain postfix, exim or another MTA, it was omitted because it is very tricky to set up correctly.
+
+### Troubleshooting
+
+View the container logs: `./launcher logs my_container`
+
+Spawn a shell inside your container using `./launcher enter my_container`. This is the most foolproof method if you have host root access.
+
+If you see network errors trying to retrieve code from `github.com` or `rubygems.org` try again - sometimes there are temporary interruptions and a retry is all it takes.
+
+Behind a proxy network with no direct access to the Internet? Add proxy information to the container environment by adding to the existing `env` block in the `container.yml` file: