Remove old production installation instructions

Author: fbacall

docs/install.md

@@ -226,43 +226,3 @@ Then go to the applications Rails console:
 Find the user and assign them the administrative role. This can be completed by running this (where myemail@domain.co is the email address you used to register with):
 
     2.2.6 :001 > User.find_by_email('myemail@domain.co').update(role: Role.find_by_name('admin'))
-
-## Production
-
-Although designed for CentOS, this document can be followed quite closely to set up a Rails app to work with Apache and Passenger:
-
-    https://www.digitalocean.com/community/tutorials/how-to-setup-a-rails-4-app-with-apache-and-passenger-on-centos-6
-
-To set up TeSS in production, do:
-
-    bundle exec rake db:setup RAILS_ENV=production
-
-which will do db:create, db:schema:load, db:seed. If you want the DB dropped as well:
-
-    bundle exec rake db:reset RAILS_ENV=production
-
-...which will do db:drop, db:setup
-
-    unset XDG_RUNTIME_DIR
-
-(may need setting in ~/.profile or similar if rails console moans about permissions.)
-
-Delete all from Solr if need be and reindex it:
-
-    curl http://localhost:8983/solr/update?commit=true -d  '<delete><query>*:*</query></delete>'
-
-    bundle exec rake sunspot:solr:reindex RAILS_ENV=production
-
-Create an admin user and assign it appropriate 'admin' role bu looking up that role in console in model Role (default roles should be created automatically).
-
-The first time and each time a css or js file is updated:
-
-    bundle exec rake assets:clean RAILS_ENV=production
-
-    bundle exec rake assets:precompile RAILS_ENV=production
-
-Restart your Web server.
-
----
-
-****