X-Git-Url: https://git.openstreetmap.org./rails.git/blobdiff_plain/eba12dc876709d335c378beb67b7b8ae9f7ef10c..b1d15b29b0c3e4acb3dd60971b3dded30d7466e8:/CONFIGURE.md

diff --git a/CONFIGURE.md b/CONFIGURE.md
index 3c46e6130..af93dcaef 100644
--- a/CONFIGURE.md
+++ b/CONFIGURE.md
@@ -144,8 +144,6 @@ If you want to deploy `openstreetmap-website` for production use, you'll need to
 
 * It's not recommended to use `rails server` in production. Our recommended approach is to use [Phusion Passenger](https://www.phusionpassenger.com/). Instructions are available for [setting it up with most web servers](https://www.phusionpassenger.com/documentation_and_support#documentation).
 * Passenger will, by design, use the Production environment and therefore the production database - make sure it contains the appropriate data and user accounts.
-* Your production database will also need the extensions and functions installed - see [INSTALL.md](INSTALL.md)
 * The included version of the map call is quite slow and eats a lot of memory. You should consider using [CGIMap](https://github.com/zerebubuth/openstreetmap-cgimap) instead.
 * Make sure you generate the i18n files and precompile the production assets: `RAILS_ENV=production rake i18n:js:export assets:precompile`
 * Make sure the web server user as well as the rails user can read, write and create directories in `tmp/`.
-* If you expect to serve a lot of `/changes` API calls, then you might also want to install the shared library versions of the SQL functions.