feat: update instructions

Author: elasticspoon

CONTRIBUTING.md

@@ -41,10 +41,13 @@ You might also want to try VSCode with [this WSL extension](https://marketplace.
    - mise will automatically install and manage the Ruby version specified in [`.ruby-version`](.ruby-version) with `mise i`
    - Verify that mise is working by running `mise --version`
 2. Install MySQL
-   - **macOS**: Use Homebrew - see [MySQL Homebrew installation guide](https://formulae.brew.sh/formula/mysql)
-   - **Windows**: Use WSL2 with Ubuntu - follow [MySQL WSL installation guide](https://dev.mysql.com/doc/mysql-installation-excerpt/8.0/en/linux-installation.html)
-   - **Linux/Ubuntu**: Follow [official MySQL APT repository installation](https://dev.mysql.com/doc/mysql-installation-excerpt/8.0/en/linux-installation-apt-repo.html)
-   - For Docker setup (recommended), see the README for MySQL container setup instructions
+   - **macOS**: [Use Homebrew](https://formulae.brew.sh/formula/[email protected])
+   - **Windows**: Use WSL2 with Ubuntu - follow [the MariaDB install guide from digital ocean](https://www.digitalocean.com/community/tutorials/how-to-install-mariadb-on-ubuntu-20-04#step-1-installing-mariadb)
+
+   - **Linux/Ubuntu**: Follow [the MariaDB install guide from digital ocean](https://www.digitalocean.com/community/tutorials/how-to-install-mariadb-on-ubuntu-20-04#step-1-installing-mariadb)
+   - Alternative (Docker): with docker installed run `mise docker-db` to start
+     the DB only (after cloning the repo)
+
 3. Clone the project and switch to its directory
 4. Run `mise setup`
 5. Run `mise server` and visit <http://localhost:3000/> to see the AWBW portal page.
@@ -63,7 +66,7 @@ For Docker-based development (recommended):
 
 ## Credentials
 
-These credentials also work for staging:
+These credentials also work for [staging](https://awbw-staging-xzek4.ondigitalocean.app/):
 
 - User
   - email: <[email protected]>
@@ -76,22 +79,17 @@ These credentials also work for staging:
 
 [![Open in GitHub Codespaces](https://github.com/codespaces/badge.svg)](https://codespaces.new/rubyforgood/awbw/tree/main?quickstart=1)
 
-[![Clone and open in VSCode Dev Container](https://img.shields.io/static/v1?label=Dev%20Containers&message=Clone%20and%20Open%20in%20VSCode&color=blue&logo=visualstudiocode)](https://vscode.dev/redirect?url=vscode://ms-vscode-remote.remote-containers/cloneInVolume?url=https://github.com/rubyforgood/awbw)
-
 1. Create the container:
    - To run the container on a Github VM, follow the Codespace link above. You can connect to the Codespace using VSCode or the VSCode web editor.
    - Or follow instructions to [create a new Codespace.](https://docs.github.com/en/codespaces/developing-in-a-codespace/creating-a-codespace-for-a-repository)
-   - To clone this repo and run the container locally, follow instructions to [install VSCode and Docker](https://code.visualstudio.com/docs/devcontainers/containers). Click the Dev Container link above. Don't forget to add a git remote pointing to your fork once the container is setup and you want to push changes.
-2. Wait for the container to start. This will take a few (10-15) minutes since Ruby needs to be installed, the database needs to be created, and the `bin/setup` script needs to run
-3. Run `bin/start`. On the Ports tab, visit the forwarded port 3000 URL marked as Application to see the AWBW portal page.
+2. Wait for the container to start. This will take a few (10-15) minutes since Ruby needs to be installed, the database needs to be created, and the `mise setup` script needs to run
+3. Run `mise server`. On the Ports tab, visit the forwarded port 3000 URL marked as Application to see the AWBW portal page.
 4. Login as a sample user with the default [credentials](#credentials).
 
 ## Troubleshooting 👷🏼‍♀️
 
 Please let us know by opening up an issue! We have many new contributors come through and it is likely what you experienced will happen to them as well.
 
-- _"My RBENV installation didn't work!"_ - The rbenv repository provides a [rbenv-doctor script](https://github.com/rbenv/rbenv-installer#rbenv-doctor) to verify the installation and check if a ruby version is installed
-
 # 🤝 Code Contribution Workflow
 
 1. **Identify an unassigned issue**. Read more [here](#issues) about how to pick a good issue.
@@ -131,17 +129,8 @@ Users that are frequent contributors and are involved in discussion (join the sl
 
 If starting server directly, via `rail s` or `rail console`, or built-in debugger in RubyMine, or running `bundle exec rspec path/to/spec.rb:line_no`, then you can use `binding.pry` to debug. Drop the pry where you want the execution to pause.
 
-If starting via Procfile with `bin/start`, then drop a `binding.remote_pry` into the line where you want execution to pause at. Then run `pry-remote` in the terminal to connect to it.
-<https://github.com/Mon-Ouie/pry-remote>
-
 If you want to connect via Shopify Ruby LSP VSCode extension or rdbg, start the server with `bundle exec rdbg -O -n -c -- bin/rails server -p 3000`
 
-### Codespaces
-
-When running tests in browser, visit the forwarded port 6080 URL to see the browser in Codespaces. You can also visit this port to access the GUI desktop in Codespaces.
-
-In VSCode Run and Debug view, there are some helpful defaults for running RSpec tests in browser at your cursor as well as attaching to a live server. Make sure the Ruby LSP server is started before debugging.
-
 ## Squashing commits
 
 Consider the balance of "polluting the git log with commit messages" vs. "providing useful detail about the history of changes in the git log". If you have several smaller commits that serve a one purpose, you are encouraged to squash them into a single commit. There's no hard and fast rule here about this (for now), just use your best judgement. Please don't squash other people's commits. Everyone who contributes here deserves credit for their work! :)
@@ -186,8 +175,8 @@ Before submitting a pull request, run all tests and lints. Fix any broken tests
 
 #### Local testing
 
-- Run all tests with `bundle exec rspec`
-- You can run a single test with `bundle exec rspec {path_to_test_name}_spec.rb` or on a specific line by appending `:LineNumber`
+- Run all tests with `mise spec` (or `mise docker-spec` if using docker)
+- You can run a single test with `mise spec {path_to_test_name}_spec.rb` or on a specific line by appending `:LineNumber`
 - If you need to skip a failing test, place `pending("Reason you are skipping the test")` into the `it` block rather than skipping with `xit`. This will allow rspec to deliver the error message without causing the test suite to fail.
 
 ```ruby

mise.toml

@@ -9,6 +9,10 @@ run = "bin/setup"
 description = "Start the rails server"
 run = "bin/rails s"
 
+[tasks.spec]
+description = "Run RSpec tests"
+run = "bundle exec rspec"
+
 [tasks.docker-up]
 description = "Start Docker containers for development"
 run = "docker compose up -d"
@@ -23,7 +27,7 @@ run = "docker compose logs -f"
 
 [tasks.docker-db]
 description = "Starts a MySql database in docker"
-run = "docker compose up -d db"
+run = "docker compose up -d database"
 
 [tasks.docker-console]
 depends = ["docker-up"]
@@ -39,3 +43,7 @@ run = "docker compose exec web bin/rails dbconsole"
 depends = ["docker-up"]
 description = "Provide commands to exec from the docker container. Ex: mise docker-exec rails db:migrate"
 run = "docker compose exec web"
+
+[tasks.docker-spec]
+description = "Run RSpec tests in Docker"
+run = "docker compose exec -e RAILS_ENV=test web bundle exec rspec"