diff options
-rw-r--r-- | developers/index.md | 12 | ||||
-rw-r--r-- | getting_started.md | 12 | ||||
-rw-r--r-- | installing/exim4.md | 2 | ||||
-rw-r--r-- | installing/manual_install.md | 8 |
4 files changed, 19 insertions, 15 deletions
diff --git a/developers/index.md b/developers/index.md index a358b2d3f..85ed3f80f 100644 --- a/developers/index.md +++ b/developers/index.md @@ -39,11 +39,13 @@ title: For developers * Installing the software is a little involved, though it's getting easier. If you stick to Debian or Ubuntu, it should be possible to get a running version - within a few hours. The documentation is in - [INSTALL.md](https://github.com/mysociety/alaveteli/blob/develop/doc/INSTALL.m - d). There is an [Alaveteli EC2 AMI]({{ site.baseurl }}installing/ami/) that - might help you get up and running quickly. [Get in - touch](http://www.alaveteli.org/contact/) on the project mailing list or IRC + within a few hours. If you've got your own server, run the + [installation script]({{ site.baseurl }}installing/script/), or follow the + instructions for a + [manual installation]({{ site.baseurl }}installing/manual_install/). + Alternatively, there's an [Alaveteli EC2 AMI]({{ site.baseurl }}installing/ami/) + that might help you get up and running quickly. + [Get in touch](http://www.alaveteli.org/contact/) on the project mailing list or IRC for help. * A standard initial step for customising your deployment is [writing a diff --git a/getting_started.md b/getting_started.md index 3df3b286c..c8dd9d0cf 100644 --- a/getting_started.md +++ b/getting_started.md @@ -188,8 +188,7 @@ custom homepage, different fonts, etc; however, the more you customise the site, the harder it is to upgrade in the future; and you'll need a developer and/or designer to help do these customisations. We call the custom set of colours, fonts, logos etc a "theme"; there are some notes for developers about -[writing a -theme](https://github.com/mysociety/alaveteli/blob/master/doc/THEMES.md). You +[writing a theme]({{ site.baseurl }}customising/themes/). You might spend anywhere between 1 and 15 days on this. ### Legislative differences @@ -237,10 +236,11 @@ Now is also a good time to start thinking about some of your standard emails that you'll be sending out in response to common user queries and administrative tasks -- for example, an email that you send to IT departments asking them to whitelist emails from your Alaveteli website (if your emails are -being marked as spam). Review the [Administrator's -Manual](/running/admin_manual.md) for details on some of the common administrative tasks. There is a list of the -standard emails used by WhatDoTheyKnow on the [FOI Wiki]( -http://foiwiki.com/foiwiki/index.php/Common_WhatDoTheyKnow_support_responses). +being marked as spam). See the +[Administrator's Manual]({{ site.baseurl }}running/admin_manual/) for details +on some of the common administrative tasks. There is a list of the +standard emails used by WhatDoTheyKnow on the +[FOI Wiki](http://foiwiki.com/foiwiki/index.php/Common_WhatDoTheyKnow_support_responses). ### Other software customisations diff --git a/installing/exim4.md b/installing/exim4.md index 4cb056a26..98438f468 100644 --- a/installing/exim4.md +++ b/installing/exim4.md @@ -101,6 +101,8 @@ yours does, you will need to rename it before running `update-exim4.conf`. `dc_local_interfaces='0.0.0.0 ; ::1'`, and `dc_other_hostnames='<your-host-name>'`) +<a name="troubleshooting"> </a> + ## Troubleshooting To test mail delivery, run: diff --git a/installing/manual_install.md b/installing/manual_install.md index a9580e402..586ad68a0 100644 --- a/installing/manual_install.md +++ b/installing/manual_install.md @@ -492,10 +492,10 @@ things that can be automated for deployment. First, you need to check that your MTA is delivering relevant incoming emails to the `script/mailin` command. There are various - ways of setting your MTA up to do this; we have documented one way - of doing it in Exim at `doc/INSTALL-exim4.conf`, including a - command you can use to check that the email routing is set up - correctly. + ways of setting your MTA up to do this; we have documented + [one way of doing it]({{ site.baseurl }}installing/exim4/#troubleshooting) + in Exim, including a command you can use to check that the email + routing is set up correctly. Second, you need to test that the mailin script itself is working correctly, by running it from the command line, First, find a |