Update README.md

Author: Jayprakash-SE

README.md

@@ -14,74 +14,3 @@ workflow that adapts to the conventions of all groups.
 ## Testing
 
 `pip install tox` into your virtualenv, then `tox`.
-
-## Deployment
-
-Ensure you have the necessary libraries by running `pip install -r requirements-dev.txt`
-in a virtualenv of your choosing.
-
-1. Ensure all changes are committed
-2. Run the tests (`tox`)
-3. Deploy to the dev instance with `fab deploy`. Ensure the script
-   runs successfully.
-   1. Check that the [the dev site](https://montage-dev.toolforge.org/meta/)
-      came back up fine.
-   2. Log in and test things out.
-   3. Check the [montage-dev sentry (devlabs)](https://sentry.io/organizations/hatnote/issues/?environment=devlabs&project=3532775)
-4. Use [the audit log](https://montage.toolforge.org/montage/v1/logs/audit)
-   to check that the production instance isn't in active use.
-5. Deploy to the production instance with `fab deploy:tool=montage`
-   1. Check that the [the production site](https://montage.toolforge.org/montage/meta/)
-      came back up fine.
-   2. Log in and test things out.
-   3. Check the [montage sentry (prod)](https://sentry.io/organizations/hatnote/issues/?environment=prod&project=3532775)
-
-Some tips (at the time of writing):
-
-- `fab deploy` without arguments will deploy `master` to `montage-dev`.
-  - To change this, use a command of this format:
-    `fab deploy:branch=other-branch,tool=montage-beta`
-  - It will fail with a helpful message if your branch is not sync'd
-    with origin. Push those commits!
-- If you see a huge golang stack trace from `fab deploy`, it's likely
-  [this bug](https://phabricator.wikimedia.org/T219070). These seem to
-  fix themselves, come back later if you can, otherwise check out the
-  thread for details on using `GOMAXPROCS`.
-- All this only deploys the backend for now.
-
-### Installing on toolforge from scratch
-
-2024-04-23
-
-1. Create new $HOME/www/python
-1. Symlink src to repo clone
-1. Use webservice to create new venv
-   - See notes below
-1. Create / copy over prod config
-1. Create / copy over uwsgi.ini
-1. Upload / copy over static
-   - cp -r ~/(ORIG_LOCATION)/static/ ~/www/python/src/montage/static/
-
-#### venv notes
-
-This mostly works: https://wikitech.wikimedia.org/wiki/Help:Toolforge/Web/Python#Creating_a_virtual_environment
-
-But before that you should install mysqlclient explicitly:
-
-```
-export MYSQLCLIENT_CFLAGS="-I/usr/include/mariadb/"
-export MYSQLCLIENT_LDFLAGS="-L/usr/lib/x86_64-linux-gnu/ -lmariadb"
-pip install mysqlclient
-```
-
-From https://wikitech.wikimedia.org/wiki/Help:Toolforge/Database#Python:_Django
-
-## Database administration notes
-
-With the move to mariadb, the easiest way to access Montage's own data (not the replicas) is:
-
-```
-# on toolforge, become montage
-$ sql tools
-> use s53490__montage;s
-```