ibi-group · binh-dam-ibigroup · Jun 6, 2016 · Jun 6, 2016 · Jun 6, 2016 · Jun 6, 2016
diff --git a/.github/workflows/codeql-analysis.yml b/.github/workflows/codeql-analysis.yml
@@ -15,10 +15,10 @@ name: "CodeQL"
 
 on:
   push:
-    branches: [ "dev", master ]
+    branches: [ "dev", master, "mtc-deploy" ]
   pull_request:
     # The branches below must be a subset of the branches above
-    branches: [ "dev" ]
+    branches: [ "dev", "mtc-deploy" ]
   schedule:
     - cron: '24 19 * * 6'
 

diff --git a/.github/workflows/node-ci.yml b/.github/workflows/node-ci.yml
@@ -16,10 +16,12 @@ jobs:
       - uses: actions/setup-python@v2
         with:
           python-version: '3.x'
-      - name: Install mkdocs
+      - name: Install mkdocs and plugins
         run: |
           pip install Jinja2==3.0.3 mkdocs
           mkdocs --version
+          pip install mkdocs-macros-plugin
+          pip install requests
       - name: Use Node.js 14.x
         uses: actions/setup-node@v1
         with:

diff --git a/.gitignore b/.gitignore
@@ -22,9 +22,13 @@ configurations/*
 !configurations/default
 !configurations/test
 !configurations/end-to-end
+!configurations/mtc-docs
 dist
 assets
 
+# Mkdocs local build
+target/
+
 # Secret config files
 env.yml
 env.yml-original

diff --git a/.readthedocs.yml → .readthedocs.yaml b/.readthedocs.yml → .readthedocs.yaml
@@ -8,7 +8,12 @@ version: 2
 build:
   os: ubuntu-22.04
   tools:
-    python: "3.11"
+    python: "3.13"
+
+# Install mkdocs macros and other plugins
+python:
+  install:
+    - requirements: docs/requirements.txt
 
 mkdocs:
   configuration: mkdocs.yml
diff --git a/configurations/default/env.yml.tmp b/configurations/default/env.yml.tmp
@@ -2,10 +2,10 @@ AUTH0_CLIENT_ID: your-auth0-client-id
 AUTH0_CONNECTION_NAME: your-auth0-connection-name
 AUTH0_DOMAIN: your-auth0-domain
 BUGSNAG_KEY: optional-bugsnag-key
-MAP_BASE_URL: optional-map-tile-url
 MAPBOX_ACCESS_TOKEN: your-mapbox-access-token
 MAPBOX_MAP_ID: mapbox/outdoors-v11
 MAPBOX_ATTRIBUTION: <a href="https://www.mapbox.com/about/maps/" target="_blank">&copy; Mapbox &copy; OpenStreetMap</a> <a href="https://www.mapbox.com/map-feedback/" target="_blank">Improve this map</a>
+MAP_BASE_URL: optional-map-tile-url
 # MAP_BASE_URL: http://tile.openstreetmap.org/{z}/{x}/{y}.png # Uncomment it if maps are gray
 SLACK_CHANNEL: optional-slack-channel
 SLACK_WEBHOOK: optional-slack-webhook
@@ -22,6 +22,6 @@ GRAPH_HOPPER_KEY: your-graph-hopper-key
 #      - 6
 #      - -46
 #      - 83
-GOOGLE_ANALYTICS_TRACKING_ID: optional-ga-key
 # GRAPH_HOPPER_POINT_LIMIT: 10 # Defaults to 30
+GOOGLE_ANALYTICS_TRACKING_ID: optional-ga-key
 DISABLE_AUTH: true
diff --git a/configurations/mtc-docs/.readthedocs.yaml b/configurations/mtc-docs/.readthedocs.yaml
@@ -0,0 +1,20 @@
+# Read the Docs configuration file for MkDocs projects
+# See https://docs.readthedocs.io/en/stable/config-file/v2.html for details
+
+# Required
+version: 2
+
+# Set the version of Python and other tools you might need
+build:
+  os: ubuntu-22.04
+  tools:
+    python: "3.13"
+
+# Install mkdocs macros and other plugins
+# Per readthedocs: paths are relative to the root of the project.
+python:
+  install:
+    - requirements: docs/requirements.txt
+
+mkdocs:
+  configuration: configurations/mtc-docs/mkdocs-mtc.yml
diff --git a/configurations/mtc-docs/mkdocs-mtc.yml b/configurations/mtc-docs/mkdocs-mtc.yml
@@ -0,0 +1,29 @@
+INHERIT: ../../mkdocs.yml
+site_name: Transit Data Manager Docs
+docs_dir: ../../docs
+
+extra:
+  product_name: MTC Transit Data Manager (TDM)
+  support_email: transitdata@511.org
+
+nav:
+- Home: 'index.md'
+- Data Manager:
+  - 'Introduction': 'user/introduction.md'
+  - 'Managing Projects & Feeds': 'user/managing-projects-feeds.md'
+  - 'Publishing Feeds': 'user/publishing-feeds.md'
+  - 'Merging Feeds': 'user/merging-feeds.md'
+  - 'Feed Version Summary': 'user/feed-version-summary.md'
+  - 'Managing Users': 'user/managing-users.md'
+  - 'Service Alerts Manager': 'user/service-alerts.md'
+  - 'Searching for Routes and Stops': 'user/searching-routes-stops.md'
+  - 'GTFS+ Editor': 'user/gtfs-plus-editor.md'
+- 'GTFS Editor':
+  - Getting Started: 'user/editor/getting-started.md'
+  - Stops: 'user/editor/stops.md'
+  - Routes: 'user/editor/routes.md'
+  - Patterns: 'user/editor/patterns.md'
+  - Schedules: 'user/editor/schedules.md'
+  - Fares: 'user/editor/fares.md'
+- Appendices:
+  - GTFS Validation Warnings: 'user/appendix-gtfs-warnings.md'
diff --git a/docs/dev/development.md b/docs/dev/development.md
@@ -49,4 +49,4 @@ yarn start -- --config /path/to/config
 
 The e2e tests have been Dockerized, which allows them to be run easily anywhere `docker compose` works. To run them on localhost, first create a `.env` file in the `__tests__/e2e`. `docker compose` will alert you as to which variables must be present.
 
-To run the tests, run `docker compose -f docker compose.yml up --abort-on-container-exit` in the `__tests__/e2e/` directory.
+To run the tests, run `docker compose -f docker-compose.yml up --abort-on-container-exit` in the `__tests__/e2e/` directory.
diff --git a/docs/img/affected-service.png b/docs/img/affected-service.png
diff --git a/docs/img/agency-filter.png b/docs/img/agency-filter.png
diff --git a/docs/img/alert-editor.png b/docs/img/alert-editor.png
diff --git a/docs/img/alerts-parent-station.png b/docs/img/alerts-parent-station.png
diff --git a/docs/img/alerts-viewer.png b/docs/img/alerts-viewer.png
diff --git a/docs/img/auto-publish-feed.png b/docs/img/auto-publish-feed.png
diff --git a/docs/img/auto-publish-status.png b/docs/img/auto-publish-status.png
diff --git a/docs/img/configuration-editor.png b/docs/img/configuration-editor.png
diff --git a/docs/img/configurations-viewer.png b/docs/img/configurations-viewer.png
diff --git a/docs/img/create-project.png b/docs/img/create-project.png
diff --git a/docs/img/editor-session-lock.png b/docs/img/editor-session-lock.png
diff --git a/docs/img/editor-welcome.png b/docs/img/editor-welcome.png
diff --git a/docs/img/feed-manager-publish.png b/docs/img/feed-manager-publish.png
diff --git a/docs/img/feed-manager-published.png b/docs/img/feed-manager-published.png
diff --git a/docs/img/feed-profile.png b/docs/img/feed-profile.png
diff --git a/docs/img/feed-transformation-results.png b/docs/img/feed-transformation-results.png
diff --git a/docs/img/feed-version-navigator.png b/docs/img/feed-version-navigator.png
diff --git a/docs/img/filter-alerts.png b/docs/img/filter-alerts.png
diff --git a/docs/img/filter-configurations.png b/docs/img/filter-configurations.png
diff --git a/docs/img/gtfs-map-search-alert.png b/docs/img/gtfs-map-search-alert.png
diff --git a/docs/img/gtfs-map-search-config.png b/docs/img/gtfs-map-search-config.png
diff --git a/docs/img/gtfsplus-editor-nav.png b/docs/img/gtfsplus-editor-nav.png
diff --git a/docs/img/gtfsplus-editor-route-attr-empty.png b/docs/img/gtfsplus-editor-route-attr-empty.png
diff --git a/docs/img/gtfsplus-editor-route-attr.png b/docs/img/gtfsplus-editor-route-attr.png
diff --git a/docs/img/gtfsplus-editor.png b/docs/img/gtfsplus-editor.png
diff --git a/docs/img/gtfsplus-publish.png b/docs/img/gtfsplus-publish.png
diff --git a/docs/img/gtfsplus-summary.png b/docs/img/gtfsplus-summary.png
diff --git a/docs/img/hours-per-mode.png b/docs/img/hours-per-mode.png
diff --git a/docs/img/merge-feeds-button.png b/docs/img/merge-feeds-button.png
diff --git a/docs/img/merge-feeds-result.png b/docs/img/merge-feeds-result.png
diff --git a/docs/img/new-alert-button.png b/docs/img/new-alert-button.png
diff --git a/docs/img/normalize-stop-times.png b/docs/img/normalize-stop-times.png
diff --git a/docs/img/pattern-add-stop.png b/docs/img/pattern-add-stop.png
diff --git a/docs/img/pattern-stop-warning.png b/docs/img/pattern-stop-warning.png
diff --git a/docs/img/publish-blocking-issue.png b/docs/img/publish-blocking-issue.png
diff --git a/docs/img/stops-routes-configuration.png b/docs/img/stops-routes-configuration.png
diff --git a/docs/img/timetable-selector.png b/docs/img/timetable-selector.png
diff --git a/docs/img/timetable-shortcuts.png b/docs/img/timetable-shortcuts.png
diff --git a/docs/img/transform-normalize-field.png b/docs/img/transform-normalize-field.png
diff --git a/docs/img/transform-route-attr-from-csv.png b/docs/img/transform-route-attr-from-csv.png
diff --git a/docs/img/transform-route-attr-from-version.png b/docs/img/transform-route-attr-from-version.png
diff --git a/docs/img/transform-table-from-csv.png b/docs/img/transform-table-from-csv.png
diff --git a/docs/img/transform-table-from-version.png b/docs/img/transform-table-from-version.png
diff --git a/docs/img/trips-per-date.png b/docs/img/trips-per-date.png
diff --git a/docs/img/trips-per-hour-histogram.png b/docs/img/trips-per-hour-histogram.png
diff --git a/docs/img/version-timetables.png b/docs/img/version-timetables.png
diff --git a/docs/index.md b/docs/index.md
@@ -1,7 +1,9 @@
-# Arcadis TRANSIT-data-tools
-
-The Arcadis TRANSIT-data-tools suite provides web-based tools for creating, managing, evaluating, and publishing transit data, specifically data stored in the General Transit Feed Specification (GTFS) format.
+# {{ product_name }}
+The {{ product_name }} suite provides web-based tools for creating, managing, evaluating, and publishing transit data, specifically data stored in the General Transit Feed Specification (GTFS) format.
 
 ![feed-profile](https://datatools-builds.s3.amazonaws.com/docs/intro/feed-profile.png)
 
-To get started, select a topic from the table of contents on the left pane.
+To get started, click a topic from the table of contents on the left pane.
+
+## Contact
+If users need to report bugs or require further assistance, please email [{{ support_email }}](mailto:{{ support_email }}).
diff --git a/docs/requirements.txt b/docs/requirements.txt
@@ -0,0 +1,4 @@
+# Pin the mkdocs version so that readthedocs uses the same version as this repo's CI job.
+# (Otherwise because the project is from before 2019, readthedocs uses a super old mkdocs 0.17.3.)
+mkdocs==1.6.1
+mkdocs-macros-plugin
diff --git a/docs/style.css b/docs/style.css
@@ -2,15 +2,25 @@ body {
   font-family: Arial, Helvetica, sans-serif;
 }
 
+/*Ignore first heading in page in TOC list*/
+.toctree-l4:first-child {
+    display: none;
+}
+
 h1, h2, h3 {
   color: #015f97;
   font-family: Arial, Helvetica, sans-serif;
 }
 
-.img-center {
+img:not(img[alt=screenshot]) {
+  min-width: 300px;
   margin-left: auto;
   margin-right: auto;
-  width: 300px;
+  max-width: 90%;
+}
+
+.section p:has(img:not(img[alt="screenshot"])) {
+  text-align: center;
 }
 
 /* Make all images responsive */

diff --git a/docs/user/editor/fares.md b/docs/user/editor/fares.md
@@ -33,13 +33,13 @@ To edit fare rules, you must first create and save a fare with attributes. After
 2. **From/to zone** - applies to any itinerary that travels from the origin zone to the destination zone
 3. **Contains zone** - applies to any itinerary that passes through *each* `contains` zone
 
-<img src="https://datatools-builds.s3.amazonaws.com/docs/fares/edit-fare-rules.png" style="box-shadow: 3px 3px 3px gray; border-radius: 10px; width: 600px">
+![Fare rule editor](https://datatools-builds.s3.amazonaws.com/docs/fares/edit-fare-rules.png)
 
 ### Creating fare zones
 
 To create a fare zone, you must first select a stop that you would like to include in the zone by clicking the location pin icon on the sidebar and selecting one of the stop names. Next, click in the `zone_id` dropdown and begin typing the new `zone_id`. Click `Create new zone: [zone_id]` and then save the stop. Repeat for as many zones as needed.
 
-<img src="https://datatools-builds.s3.amazonaws.com/docs/fares/add-fare-zone.png" style="box-shadow: 3px 3px 3px gray; border-radius: 10px;">
+![Add fare zone](https://datatools-builds.s3.amazonaws.com/docs/fares/add-fare-zone.png)
 
 ### Tutorial Video: Editing/Creating Fares
 <iframe 

diff --git a/docs/user/editor/getting-started.md b/docs/user/editor/getting-started.md
@@ -1,6 +1,18 @@
 # Getting Started
 
-The GTFS Editor (or Editor) allows users to edit GTFS feeds imported from the Data Manager (see [Managing Project & Feeds](../managing-projects-feeds.md)) or create GTFS feeds completely from scratch.
+## Getting started
+
+The GTFS Editor (or Editor) allows users to edit GTFS feeds imported from the Data Manager (see [Loading Feed Versions into Editor](../../user/managing-projects-feeds/#loading-feed-versions-into-editor)) or create GTFS completely from scratch. The following prompt will appear when you first enter the editor (by clicking 'Edit feed').
+
+![gtfs editor welcome screen](../../img/editor-welcome.png)
+
+## Editing sessions
+Only one editing session per feed source is permitted in order to prevent users concurrently editing data and potentially making incoherent or incompatible changes (e.g., user A adds a pattern stop at position 4 while user B removes a pattern stop at position 4). Because of the highly interrelated nature of GTFS tables locking these sessions is required.
+
+If a second user attempts to edit a feed that with an editing session already underway, they will be locked from editing and must wait until the current user has completed their editing session or choose to override the other editor (this should only be done with care in order not to negatively impact another user's session).
+
+![editor session lock warning](../../img/editor-session-lock.png)
+
 
 ## Saving in the Editor
 
@@ -24,9 +36,9 @@ Some tables are nested underneath these primary tables. Here's how to find them
 
 ## Quick access toolbar
 
-In the bottom, righthand corner of the Editor, you'll find the quick access toolbar that has a few convenient features:
+In the bottom, righthand corner of the Editor, you'll find the quick access toolbar that has a few convenient features you might need while editing.
 
-<img src="https://datatools-builds.s3.amazonaws.com/docs/intro/quick-access-toolbar.png" style="box-shadow: 3px 3px 3px gray; border-radius: 10px; width: 500px;">
+![quick access toolbar](https://datatools-builds.s3.amazonaws.com/docs/intro/quick-access-toolbar.png)
 
 From left to right, these functions are:
 

diff --git a/docs/user/editor/patterns.md b/docs/user/editor/patterns.md
@@ -14,6 +14,13 @@ To begin editing trip patterns, first click the `Routes` tab (outlined in red).
 - **Direction:** Specifies whether the pattern is inbound or outbound. This corresponds to the `direction_id` field in GTFS. All trips associated with this pattern will be assigned the direction provided here.
 - **Editing schedules:**
 Click `Edit schedules` to begin creating or editing trips/frequencies for a trip pattern. You will be redirected to the Schedule Editor. For more information on creating schedules for a pattern, see [Trips](schedules).
+- **Use timetables/frequencies** - whether the pattern uses timetables, i.e., individual entries for each trip made over the course of a day, or frequencies, which define varying frequencies (or headways) according to time intervals over the course of a day.
+- **Direction** - corresponds to the `direction_id` field in GTFS. All trips associated with this pattern will be assigned the direction provided here.
+
+## Editing schedules
+Click `Edit schedules` to begin creating or editing trips/frequencies for a trip pattern. You will be redirected to the Schedule Editor.
+
+For more information on creating schedules for a pattern, [see the Trips section](schedules).
 
 To add a pattern, click the `+ New pattern` button (highlighted in yellow).
 
@@ -35,18 +42,16 @@ To reverse the sequence of stops for a pattern, click the button with opposing a
 
 ## Stop sequence
 ### Adding stops
-To start creating a pattern, click the `+ Add stop` button. From here, zoom in on the map and add stops by clicking on them and clicking the green plus symbol: `+`. 
-
-Alternatively, scroll to the end of the stop sequence and click `+ Add stop by name` which will provide a dropdown of options to click from. From there, you'll have the option to add the stop to the end or to the beginning of the pattern.
+To begin constructing a pattern, click `+ Add stop`. You can then search for stops to add by name in the dropdown that appears or zoom into the map and add stops by clicking on them and clicking `+ Add stop`.
 
-<img src="https://datatools-builds.s3.amazonaws.com/docs/patterns/pattern-add-stop.png" style="box-shadow: 3px 3px 3px gray; border-radius: 10px;">
+![add stop from dropdown](../../img/pattern-add-stop.png)
 
 As you add stops, the pattern shape will update according to the street network. Keep selecting and adding stops in the sequence the route passes through them until the route is complete.
 
 ### Inserting stops mid-sequence
-First, click the `From Stops` button so that Datatools knows the pattern can be regenerated by editing stops. If you realize that you have missed a stop from the sequence, it can be added after the fact. When adding via the dropdown, stops can only be added to the end of the sequence. However, if you're adding via the map, you can choose exactly where to insert the stop.
+First, click the `From Stops` button so that Datatools knows the pattern can be regenerated by editing stops. If you realize that you have missed a stop from the sequence, it can be added after the fact. When adding via the dropdown, stops can only be added to the end of the sequence; however, if you're adding via the map, you can choose where exactly to insert the stop.
 
-<img src="https://datatools-builds.s3.amazonaws.com/docs/patterns/pattern-insert-stop.png" style="box-shadow: 3px 3px 3px gray; border-radius: 10px;">
+![insert stop from map](https://datatools-builds.s3.amazonaws.com/docs/patterns/pattern-insert-stop.png)
 
 ### Pattern stop toolbar
 The pattern stop toolbar can be found by clicking the pattern stop in the map view.
@@ -57,14 +62,28 @@ The pattern stop toolbar can be found by clicking the pattern stop in the map vi
 - **Add:** add the stop to the sequence at an additional location. This is useful for patterns that might visit the same stop more than once (e.g., loop routes).
 
 ### Changing the order of stops
-First, click the `From Stops` button so that Datatools knows the pattern can be regenerated by editing stops. If a stop is in the wrong order, you can click and drag and drop the stop from the list view into the correct sequence.
+First, click the `From Stops` button so that Datatools knows the pattern can be regenerated by editing stops. If a stop is in the wrong order, you can click and drag and drop the stop from the list view into the correct sequence. The sequence displayed on the stop being dragged will only update after being dropped into place.
 
-<img src="https://datatools-builds.s3.amazonaws.com/docs/patterns/pattern-stop-order.png" style="box-shadow: 3px 3px 3px gray; border-radius: 10px;">
+![drag and drop pattern stop](https://datatools-builds.s3.amazonaws.com/docs/patterns/pattern-stop-order.png)
 
 ### Removing stops
 Stops can be removed from the pattern by clicking the red trash (🗑) icon found in the expanded stop card or by clicking the pattern stop on the map view.
 
 ## Stop timings
+### Pattern stop colors
+Pattern stops shown in the list with an orange color represent stops that have no travel time defined. In many cases this is acceptable -- e.g., when stops along the pattern do not represent timepoints and are intended to be interpolated or are otherwise intentionally left blank.
+
+Sometimes, however, leaving travel times blank is unintentional and these values should be filled in with a mm:ss (minutes + seconds) value. Once the value is filled and saved, the orange color will change to a pale green.
+
+### Normalize stop times
+Whenever a pattern stop is added, inserted, or removed from a pattern, a warning will appear in the upper right hand corner of the screen. This message will prompt you to to adjust the default travel time for the pattern stops based on whichever action you took. For example, if stop #3 was removed, the travel time between stops #2 and #4 (now #3) may need to be increased to account for the change in distance traveled.
+
+![pattern stop warning](../../img/pattern-stop-warning.png)
+
+Once you have adjusted the stop timings, another warning will appear prompting you to click `Normalize stop times`. This button gives you a way to apply the change in pattern stop timings to any and all of the pre-existing trips for the pattern. It prevents you from needing to adjust these trips manually. After clicking `Normalize stop times`, you will be shown the following prompt asking you to define which stops you would like to normalize (the default is for all stops/stop times to be normalized). Once you confirm, you will receive a message confirming how many stop times were updated.
+
+![normalize pattern stops](../../img/normalize-stop-times.png)
+
 ### Calculate timings
 The average speed for the route can be used to calculate all the time gaps between stops in one go. A few parameters can be specified before calculating times:
 
@@ -118,13 +137,17 @@ While editing a pattern shape, there are a few behaviors you should be aware of:
 - **Cancel:** Cancel edits and leave editing mode
 
 ### Edit settings
-- **Snap to streets:** Snaps segments between handles and stops to streets. If unchecked, segments will form straight lines between handles and stops (e.g., for drawing shapes for rail lines).
+
+- **Snap mode selector** - Use the dropdown selector to choose how pattern segments between handles and stops are aligned. The available snapping modes are:
+  - **Snap to streets** - snaps segments between handles and stops to streets. Can toggle the 'Avoid highways in routing' checkbox as needed.
+  - **Snap to rail** - snaps segments between handles and stops to rail.
+  - **None** - segments will form straight lines between handles and stops.
 - **Hide stop handles:** Keeps shape segments snapped to stops. If unchecked, stop handles will become draggable. In most cases, this setting should remain checked.
 - **Hide inactive segments:** Toggles whether to show segments that are not currently being edited. 
-- **Show stops** Toggles whether stops are visible because sometimes stop markers can get in the way when trying to draw shapes.
+- **Show stops** - Toggles whether stops are visible because sometimes stop markers can get in the way when trying to draw shapes.
 - **Show tooltips:** Toggles whether to show tips when hovering over a segment, e.g. "Click to edit segment" or "Click to add control point". 
 
-<img src="https://datatools-builds.s3.amazonaws.com/docs/patterns/pattern-shape-panel.png" style="box-shadow: 3px 3px 3px gray; border-radius: 10px;">
+![pattern shape editing options](../../img/pattern-shape-panel.png)
 
 ### Editing modes
 

diff --git a/docs/user/editor/routes.md b/docs/user/editor/routes.md
@@ -42,6 +42,22 @@ Once all the required fields and any of the desired optional fields are filled i
 
 **Note:** as with all newly created items (except patterns), the new route will not be saved until the save icon (💾) is clicked.
 
+### Status
+
+There are three options for **Status**:
+
+- **In-Progress** - showing a route has not been completely entered.
+- **Pending Approval** - a route has all the information entered and is awaiting a senior person to sign it off
+- **Approved** - all the above stages have been completed.
+
+Upon editing a route, the status will automatically be set to **In Progress**. The status will need to
+be manually updated to **Approved** before it will be included in the exported feed.
+
+### Publicly visible
+
+Leave this box unchecked if you are entering a route that is not to be included in a GTFS output, or is in-progress.
+
+Routes in the Pending Approval or In Progress phase will not be publicly visible. 
 
 ## Trip Patterns
Original file line number	Diff line number	Diff line change
Expand Up		@@ -49,4 +49,4 @@ yarn start -- --config /path/to/config

		The e2e tests have been Dockerized, which allows them to be run easily anywhere `docker compose` works. To run them on localhost, first create a `.env` file in the `__tests__/e2e`. `docker compose` will alert you as to which variables must be present.

		To run the tests, run `docker compose -f docker compose.yml up --abort-on-container-exit` in the `__tests__/e2e/` directory.
		To run the tests, run `docker compose -f docker-compose.yml up --abort-on-container-exit` in the `__tests__/e2e/` directory.