Avoid bash references and bashisms as much as possible

Author: davidje13

README.md

@@ -10,7 +10,7 @@ simplified code, development, and deployment.
 
 Requires [Node.js 18 or above](https://nodejs.org/en/).
 
-```bash
+```sh
 npm start
 ```
 
@@ -26,7 +26,7 @@ You can find pre-built releases at
 [Refacto/releases](https://github.com/davidje13/Refacto/releases),
 or you can build your own:
 
-```bash
+```sh
 npm run build
 ```
 
@@ -37,7 +37,7 @@ The output is placed in `build`.
 You will need to have NodeJS 18 or newer installed in the deployment
 environment.
 
-```bash
+```sh
 cd build
 npm install --omit=dev
 ./index.js
@@ -66,7 +66,7 @@ values) can be found in
 
 Typical values to configure are:
 
-```bash
+```sh
 PORT=5000 \
 SSO_GOOGLE_CLIENT_ID="<your-google-client-id>" \
 SSO_GITHUB_CLIENT_ID="<your-github-client-id>" \

docs/CONTRIBUTING.md

@@ -2,7 +2,7 @@
 
 ## Running locally
 
-```bash
+```sh
 npm start
 ```
 
@@ -19,33 +19,33 @@ Google sign in) and data persistence, see the
 
 Run all tests:
 
-```bash
+```sh
 npm test
 ```
 
 ### Testing frontend only
 
-```bash
+```sh
 npm run test:frontend
 ```
 
 Watch mode:
 
-```bash
+```sh
 npm run test:frontend:watch
 ```
 
 ### Testing backend only
 
-```bash
+```sh
 npm run test:backend
 ```
 
 ### End-to-end tests only
 
 To automatically build and run the server, and run tests against it:
 
-```bash
+```sh
 npm run test:e2e
 ```
 
@@ -56,7 +56,7 @@ uses a mock Google single-sign-on endpoint even if you have configured
 a real client ID), then run the end-to-end tests against that
 deployment:
 
-```bash
+```sh
 TARGET_HOST=http://localhost:5000/ MODE=dev npm run test:e2e
 ```
 
@@ -65,7 +65,7 @@ larger when built in dev mode via `npm start`)
 
 Run end-to-end tests with non-headless browsers:
 
-```bash
+```sh
 HEADLESS=false npm run test:e2e
 ```
 
@@ -74,14 +74,14 @@ to `src/e2e/build/app.log`.
 
 ## Building
 
-```bash
+```sh
 npm run build
 ```
 
 The output will be placed in `build`. Specify the `PORT` environment
 variable when running (defaults to 5000):
 
-```bash
+```sh
 cd build
 npm install --omit=dev
 PORT=8080 ./index.js
@@ -116,19 +116,19 @@ and build / test dependencies should be installed with `--save-dev`.
 
 ### Examples
 
-```bash
+```sh
 cd src/frontend
 npm install --save react
 npm install --save-dev jest
 ```
 
-```bash
+```sh
 cd src/backend
 npm install --save express
 npm install --save-dev supertest
 ```
 
-```bash
+```sh
 cd src/e2e
 npm install --save-dev selenium-webdriver
 ```

docs/SECURITY.md

@@ -10,7 +10,7 @@ Deploying to a platform-as-a-service will handle this automatically.
 
 When deploying behind a proxy, you should set `TRUST_PROXY=true`:
 
-```bash
+```sh
 TRUST_PROXY=true ./index.js
 ```
 
@@ -27,7 +27,7 @@ work factor, individual salts, and a "brute-force salt".
 If you have a powerful webserver, you can increase the hash work
 factor:
 
-```bash
+```sh
 PASSWORD_WORK_FACTOR=12 ./index.js
 ```
 
@@ -54,7 +54,7 @@ constant with deployments of new versions of the app. The best place to
 store this value is in a deployment pipeline configuration, or a
 configuration server.
 
-```bash
+```sh
 PASSWORD_SECRET_PEPPER="asecretwhichmustnotbeknown" ./index.js
 ```
 
@@ -100,14 +100,14 @@ regardless of database choice. By default, a secret key of all zeros
 is used, providing no real protection. To get the benefits of data
 encryption, supply a secret key on startup.
 
-```bash
+```sh
 ENCRYPTION_SECRET_KEY="0000000000000000000000000000000000000000000000000000000000000000" ./index.js
 ```
 
 The secret key should be 32 random bytes (256 bits) encoded in
 base16 (hex). You can generate a random key with:
 
-```bash
+```sh
 ./scripts/random-secrets.js
 ```
 
@@ -138,7 +138,7 @@ deployments of new versions of the app. The best place to store this
 value is in a deployment pipeline configuration, or a configuration
 server.
 
-```bash
+```sh
 TOKEN_SECRET_PASSPHRASE="asecretwhichmustnotbeknown" ./index.js
 ```
 
@@ -181,20 +181,20 @@ will be complete.
 
 2. Enforce authorization:
 
-   ```bash
+   ```sh
    echo 'security.authorization: enabled' >> /usr/local/etc/mongod.conf
    brew services restart mongodb
    ```
 
 You can now connect as the `admin` user:
 
-```bash
+```sh
 mongo --authenticationDatabase admin -u admin -p
 ```
 
 And configure Refacto to connect as the `refacto` user:
 
-```bash
+```sh
 DB_URL="mongodb://refacto:<pass>@localhost:27017/refacto" ./index.js
 ```
 
@@ -205,7 +205,7 @@ DB_URL="mongodb://refacto:<pass>@localhost:27017/refacto" ./index.js
 To enable SSL (encrypted) communications, but without server or client
 identity checks:
 
-```bash
+```sh
 # macOS
 MONGO_VAR="/usr/local/var/mongodb"
 MONGO_CONF="/usr/local/etc/mongod.conf"
@@ -244,15 +244,15 @@ sudo service mongod restart
 
 After enabling security, change the database URL when starting Refacto:
 
-```bash
+```sh
 DB_URL="mongodb://localhost:27017/refacto?ssl=true" ./index.js
 ```
 
 Note that after enabling this, unless you also configure identity
 checks, you will need to skip certificate validation when connecting
 via the commandline:
 
-```bash
+```sh
 mongo --ssl --sslAllowInvalidCertificates
 ```
 

docs/SERVICES.md

@@ -11,28 +11,28 @@ load-balancing, configure a real database:
 
 You can specify the database connection string as:
 
-```bash
+```sh
 DB_URL="mongodb://localhost:27017/refacto" ./index.js
 ```
 
 The URL can also contain options, such as:
 
-```bash
+```sh
 DB_URL="mongodb://localhost:27017/refacto?ssl=true" ./index.js
 ```
 
 #### Installation
 
 On macOS, MongoDB can be installed with:
 
-```bash
+```sh
 brew install mongodb
 brew services start mongodb
 ```
 
 On Ubuntu, it can be installed with:
 
-```bash
+```sh
 apt install mongodb
 ```
 
@@ -48,7 +48,7 @@ the [security documentation](./SECURITY.md) for details.*
 Redis is also supported for persisting data, but is experimental and
 not recommended for production deployments.
 
-```bash
+```sh
 DB_URL="redis://localhost:6379/0" ./index.js
 ```
 
@@ -61,7 +61,7 @@ securely configure PostgreSQL than MongoDB.
 You must create a database for Refacto to use. The schema will be
 auto-generated when the app starts.
 
-```bash
+```sh
 DB_URL="postgresql://localhost:5432/refacto" ./index.js
 ```
 
@@ -89,7 +89,7 @@ You can now invoke the application with the `SSO_GOOGLE_CLIENT_ID`
 environment variable set. This applies to both local testing and
 deployments. For example:
 
-```bash
+```sh
 SSO_GOOGLE_CLIENT_ID="something.apps.googleusercontent.com" ./index.js
 ```
 
@@ -108,7 +108,7 @@ You can now invoke the application with the `SSO_GITHUB_CLIENT_ID` and
 `SSO_GITHUB_CLIENT_SECRET` environment variables set. This applies to
 both local testing and deployments. For example:
 
-```bash
+```sh
 SSO_GITHUB_CLIENT_ID="idhere" SSO_GITHUB_CLIENT_SECRET="secrethere" ./index.js
 ```
 
@@ -128,14 +128,14 @@ You can now invoke the application with the `SSO_GITLAB_CLIENT_ID`
 environment variable set. This applies to both local testing and
 deployments. For example:
 
-```bash
+```sh
 SSO_GITLAB_CLIENT_ID="idhere" ./index.js
 ```
 
 To use a self-hosted GitLab deployment, you will also need to set
 the auth and token info URLs:
 
-```bash
+```sh
 SSO_GITLAB_AUTH_URL="https://gitlab.example.com/oauth/authorize" \
 SSO_GITLAB_TOKEN_INFO_URL="https://gitlab.example.com/oauth/token/info" \
 SSO_GITLAB_CLIENT_ID="idhere" \
@@ -155,7 +155,7 @@ You will need a Giphy API key:
 You can now invoke the application with the `GIPHY_API_KEY` environment
 variable set. This applies to both local testing and deployments. For example:
 
-```bash
+```sh
 GIPHY_API_KEY="keyhere" ./index.js
 ```
 
@@ -169,6 +169,6 @@ No configuration is required.
 
 If you wish to _disable_ this integration, you can specify a blank URL:
 
-```bash
+```sh
 PASSWORD_CHECK_BASE_URL="" ./index.js
 ```