remove windows support, update contributing.md

Author: simonLeary42

CONTRIBUTING.md

@@ -1,22 +1,25 @@
 # Contributing to the Unity Web Portal
 
-## Branch Structure
-
-Each release version has its own branch. Once that version is released, the branch is locked.
-
-When submitting pull requests, the pull request should be made to the version you are targetting, assuming it is not already released.
-
 ## Conventions
 
-This code base is currently using PHP version 7.4. All files are required to be linted with PSR-12 standard. This repository will automatically check PRs for linting compliance.
+This code base is currently using PHP version 8.3.
+All files are required to be linted with PSR-12 standard.
+This repository will automatically check PRs for linting compliance.
 
 ## Development Environment
 
 ### Setting up your Environment
 
-1. Download and install [docker desktop](https://www.docker.com/products/docker-desktop/) for your appropriate OS.
-1. In `tools/docker-dev` Run the build script: `./build.sh` (mac os/linux) or `./build.bat` (windows)
-1. Run the environment: `./run.sh` (mac os/linux) or `./run.bat` (windows). Press `CTRL+C` to exit.
+1. Clone this repo (including submodules): `git clone <this-repo> --recurse-submodules`
+1. install composer
+1. install PHP dependencies: `composer update`
+1. If you're on Windows, use WSL
+1. Download and install [docker desktop](https://www.docker.com/products/docker-desktop/)
+1. In `tools/docker-dev` Run the build script: `./build.sh`
+1. Run the environment: `./run.sh`. Press `CTRL+C` to exit
+1. If you bork your LDAP or SQL server, just run `./build.sh` again
+1. Install pre-commit
+1. setup pre-commit: `pre-commit install`
 
 ### Environment Usage
 
@@ -29,25 +32,14 @@ While the environment is running, the following is accessible:
 
 ### Test Users
 
-The test environment ships with a number of users that can be used for testing. When accessing locked down portions of the portal, you will be asked for a username and password. The password is always `password`.
-
-The following users are available for testing:
-
-* `[email protected]` - admin user who is a member of pi_user1_domain_edu
-* `[email protected]` - admin user
-* `[email protected]` - user who is the owner of pi_user1_domain_edu
-* `[email protected]` - user who is the owner of pi_user2_domain_edu
-* `[email protected]` - user who is a member of pi_user1_domain_edu
-* `[email protected]` - user
-* `[email protected]` - user who is a member of pi_user2_domain_edu
-* `[email protected]` - user who is a member of pi_user2_domain_edu
-* `[email protected]` - user who has no LDAP object
-* `[email protected]` - user who has no LDAP object
-* `[email protected]` - user who has no LDAP object
-* `[email protected]` - user who is the owner of pi_user1_domain2_edu
-* `[email protected]` - user
-* `[email protected]` - user who has no LDAP object
-* `[email protected]` - user who has no LDAP object
+The test environment ships with a number of users that can be used for testing.
+When accessing locked down portions of the portal, you will be asked for a username and password.
+The password is always `password`. `tools/docker-dev/web/htpasswd` contains all valid usernames.
+
+Notable users:
+* `[email protected]` - admin, PI
+* `[email protected]` - not admin, not PI
+* `[email protected]` - does not yet have an account
 
 ### Changes to Dev Environment