diff options
| author | Louise Crow <louise.crow@gmail.com> | 2014-07-10 16:56:52 +0100 |
|---|---|---|
| committer | Louise Crow <louise.crow@gmail.com> | 2014-07-10 16:56:52 +0100 |
| commit | 95616048a07b1f34c25eb9c27875f18406a72743 (patch) | |
| tree | a75fe64914466f613f5c699ed81962fd8e132424 /docs/installing/index.md | |
| parent | 94abbed71e60f78beb5e195d00275a70ce2efc38 (diff) | |
| parent | 2def92faf3b07ffb33a1fe89dac7e4208889e54a (diff) | |
Merge branch 'gh-pages' of ssh://git.mysociety.org/data/git/public/alaveteli into gh-pages
Diffstat (limited to 'docs/installing/index.md')
| -rw-r--r-- | docs/installing/index.md | 19 |
1 files changed, 11 insertions, 8 deletions
diff --git a/docs/installing/index.md b/docs/installing/index.md index c276c3d08..50bcfd25a 100644 --- a/docs/installing/index.md +++ b/docs/installing/index.md @@ -6,17 +6,19 @@ title: Installing # Installing Alaveteli <p class="lead"> - Although you can install Alaveteli and just change it when you need it, we - recommend you adopt a way of <strong>deploying</strong> it automatically. - This has several advantages, especially for your - <a href="{{ site.baseurl }}docs/glossary/#production">production server</a>. + There are a number of ways to install Alaveteli. + We've made an Amazon Machine Image (AMI) so you can quickly deploy on + Amazon EC2 (handy if you just want to evaluate it, for example). + If you prefer to use your own server, there's an installation script + which does most of the work for you, or you can follow the manual + installation instructions. </p> ## Before you start This is important: you need to decide if you are installing Alaveteli for -[development]({{ site.baseurl }}docs/glossary/#development) or -[production]({{ site.baseurl }}docs/glossary/#production). +<a href="{{ site.baseurl }}docs/glossary/#development" class="glossary__link">development</a> or +<a href="{{ site.baseurl }}docs/glossary/#production" class="glossary__link">production</a>. A **development** site is one where you're going to change, customise, and perhaps experiment while you get it up and running. You should always do this @@ -30,9 +32,10 @@ messages switched off. It's important to be able to deploy changes to a production site quickly and efficiently, so we recommend you consider using a [deployment mechanism]({{ site.baseurl }}docs/installing/deploy/) too. -Ideally, you should also have a [staging site]({{ site.baseurl }}docs/glossary/#staging), +Ideally, you should also have a +<a href="{{ site.baseurl }}docs/glossary/#staging" class="glossary__link">staging site</a>, which is used solely to test new code in an identical environment to your -production site but before it goes live. +production site before it goes live. If you're in doubt, you're probably running a development site. Get it up and running, play with it, customise it, and -- later -- you can install it as a |