diff options
Diffstat (limited to 'doc')
-rw-r--r-- | doc/DEPLOY.md | 1 | ||||
-rw-r--r-- | doc/INSTALL.md | 6 | ||||
-rw-r--r-- | doc/TRANSLATE.md | 15 |
3 files changed, 15 insertions, 7 deletions
diff --git a/doc/DEPLOY.md b/doc/DEPLOY.md index 767f720fd..f2e643ec5 100644 --- a/doc/DEPLOY.md +++ b/doc/DEPLOY.md @@ -20,7 +20,6 @@ These are the general steps required to get your staging server up and running: * SSH to the server, change to the `deploy_to` directory * `cp releases/[SOME_DATE]/config/general.yml-example shared/general.yml` * `cp releases/[SOME_DATE]/config/database.yml-example shared/database.yml` -* `cp releases/[SOME_DATE]/config/memcached.yml-example shared/memcached.yml` * Edit those files to match your required settings * Back on your machine run `cap deploy` and it should successfully deploy * Run the DB migrations `cap deploy:migrate` diff --git a/doc/INSTALL.md b/doc/INSTALL.md index 761121139..3a911cbc8 100644 --- a/doc/INSTALL.md +++ b/doc/INSTALL.md @@ -220,12 +220,6 @@ The default theme is the "Alaveteli" theme. When you run `rails-post-deploy` (see below), that theme gets installed automatically. -You'll also want to copy `config/memcached.yml-example` to -`config/memcached.yml`. The application is configured, via the -Interlock Rails plugin, to cache content using memcached. You -probably don't want this in your development profile; the example -`memcached.yml` file disables this behaviour. - Finally, copy `config/newrelic.yml-example` to `config/newrelic.yml`. This file contains configuration information for the New Relic performance management system. By default, monitoring is switched off diff --git a/doc/TRANSLATE.md b/doc/TRANSLATE.md index abf47add3..f8b4adbcb 100644 --- a/doc/TRANSLATE.md +++ b/doc/TRANSLATE.md @@ -39,6 +39,21 @@ The release manager will also give you a **translation deadline**. After this date, you can continue to contribute new translations, but they won't make it into the release. +## General notes on translation in Transifex + +Some bits of text will have comments attached to them from the Alaveteli +application developers about the context in which the text appears in the +application - these comments will appear under the 'Details' tab for the +text in Transifex. + +Some bits of text are in the form of two bits of text separated by a `|` +character e.g. `IncomingMessage|Subject`. These represent attribute names, so +`IncomingMessage|Subject` is the subject attribute of an incoming message on +the site. You should not prioritise these types of text when translating - +they do not appear on the site anywhere at the moment, and when they do, +they will only be used in the admin interface. If you do translate them, only +translate the text after the `|`. + # Translation process: release manager's view Before the Alaveteli release manager cuts a new release branch, they |