You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The core application for Conveyal's transit data tools suite.
4
4
5
+
## Configuration
6
+
7
+
This repository serves as the front end UI for the Data Manager application. It must be run in conjunction with [datatools-server](https://github.com/conveyal/datatools-server)
8
+
5
9
## Documentation
6
10
7
-
View the [latest documentation](http://conveyal-data-tools.readthedocs.org/en/latest/) at ReadTheDocs.
11
+
View the [latest documentation](http://conveyal-data-tools.readthedocs.org/en/latest/) at ReadTheDocs for more info on deployment and development as well as a user guide.
Copy file name to clipboardExpand all lines: docs/dev/deployment.md
+41-29Lines changed: 41 additions & 29 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,27 +2,40 @@
2
2
3
3
## Prerequisites
4
4
5
-
The application features a Spark-powered Java backend and a Javascript frontend written with React and Redux. To install and deploy the application, you will need Java 8, Maven, Node/npm, yarn, and [mastarm](https://github.com/conveyal/mastarm).
5
+
The application consists of two repositories: a [Spark-powered Java backend](https://github.com/conveyal/datatools-server) and a [Javascript frontend written with React and Redux](https://github.com/conveyal/datatools-ui). To install and deploy the application, you will need Java 8, Maven, Node/npm, yarn, and [mastarm](https://github.com/conveyal/mastarm).
6
6
7
-
User athentication is done via [Auth0](http://auth0.com). You will need an Auth0 account and application to use the Data Manager.
7
+
User authentication is done via [Auth0](http://auth0.com). You will need an Auth0 account and application to use the Data Manager.
8
8
9
9
## Installation and Basic Configuration
10
10
11
11
Clone the repo and change to the project directory:
Create directories on your local machine to store the MapDB databases, GTFS feeds, and GeoJSON data. Update the following properties in `config.yml` to reflect these locations:
25
+
You'll then need to supply Auth0 account information (see below) and API keys for various services used in the application.
26
+
27
+
The default `server.yml` (for `datatools-server`) and `settings.yml` (for `datatools-ui`) should work out of the box, but you may want to specify alternative settings files outside of these repositories. These can be specified as a directory during `datatools-ui` build with mastarm:
The application back-end should now be running at `http://localhost:9000` (or whatever port you specified in `config.yml`).
125
-
The front-end assets are pointed to by the back end at whatever s3 bucket name is specified in `config.yml` at `application.assets_bucket`.
135
+
The application back-end should now be running at `http://localhost:9000` (or whatever port you specified in `server.yml`).
136
+
The front-end assets are pointed to by the back end at whatever s3 bucket name is specified in `server.yml` at `application.assets_bucket`.
126
137
127
138
## Configuring Modules
128
139
@@ -135,25 +146,26 @@ Enables the GTFS Editor module.
135
146
#### List of configuration settings
136
147
137
148
- `MAPZEN_TURN_BY_TURN_KEY`
138
-
- `mapbox`
139
-
- `access_token`
140
-
- `map_id`
149
+
- `MAPBOX_MAP_ID`
150
+
- `MAPBOX_ACCESS_TOKEN`
151
+
- `R5_URL`(optional parameter for r5 routing in editor pattern drawing)
141
152
142
153
### Validator
143
154
144
155
While the application handles basic validation even without the validator module enabled, the validator allows for enhanced accessibility- and map-based validation.
145
156
146
157
#### List of configuration settings
147
158
148
-
- `application.osm_vex`- the validator requires the URL of a running instance of the [OSM vex server](https://github.com/conveyal/vanilla-extract).
159
+
- `OSM_VEX`- `datatools-server:env.yml` the validator requires the URL of a running instance of the [OSM vex server](https://github.com/conveyal/vanilla-extract).
160
+
149
161
150
162
### Sign Configurations
151
163
152
164
Enables the sign configuration module.
153
165
154
166
#### List of configuration settings
155
167
156
-
- `use_extension`- extension to use for sign configuration
168
+
- `use_extension`- extension key to use for sign configuration
157
169
- `url`
158
170
- Requires `gtfsapi` module
159
171
@@ -163,7 +175,7 @@ Enables the real-time alerts module.
163
175
164
176
#### List of configuration settings
165
177
166
-
- `use_extension`- extension to use for sign configuration
178
+
- `use_extension`- extension key to use for sign configuration
167
179
- `url`
168
180
- Requires `gtfsapi` module
169
181
@@ -177,7 +189,7 @@ Enables the OTP automated deployments module.
177
189
178
190
#### List of configuration settings
179
191
180
-
- `application.osm_vex`- the validator requires the URL of a running instance of the [OSM vex server](https://github.com/conveyal/vanilla-extract).
192
+
- `OSM_VEX`- `datatools-server:env.yml` the validator requires the URL of a running instance of the [OSM vex server](https://github.com/conveyal/vanilla-extract).
181
193
182
194
### GTFS API
183
195
@@ -188,7 +200,7 @@ Supports other modules with API endpoints for getting GTFS entities (routes, sto
188
200
- `load_on_fetch`- whether to load GTFS feeds when new feed is detected
189
201
- `load_on_startup`- whether to load GTFS feeds on application startup
190
202
- `use_extension`- which extension to connect to
191
-
- `update_frequency`- update frequency for GTFA API (in seconds)
203
+
- `update_frequency`- update frequency for GTFS API (in seconds). Comment out to disable updates.
Copy file name to clipboardExpand all lines: docs/dev/development.md
+7-1Lines changed: 7 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,4 +10,10 @@ To kick off a development server at [http://localhost:9966](http://localhost:996
10
10
npm start
11
11
```
12
12
13
-
This will use `mastarm` to run a browserify server at the above port along with a proxy for the back-end API, which is assumed to be running on http://localhost:4000.
13
+
This will use `mastarm` to run a browserify server at the above port along with a proxy for the back-end API, which is assumed to be running on http://localhost:4000.
14
+
15
+
To optionally substitute the default configuration, provide your own directory:
0 commit comments