Skip to content

Latest commit

 

History

History
90 lines (68 loc) · 3.46 KB

Installation.md

File metadata and controls

90 lines (68 loc) · 3.46 KB
Raw

Want to get started quickly?

Install requirements

You need Node, yarn (or npm3) and watchman.

  • node -v should be >= 10.19. There might be problems it is 12 or above
  • yarn --version should be >= 1.22.0. The project will then use yarn 2 from the included file. (or npm -v should be >= 3)

You also need a C compiler:

  • Linux: GCC 4.6 or later
  • OS X: Xcode 5.0 or later
  • Windows: for example MSVC 2013 Express

Install watchman

git clone https://github.com/facebook/watchman.git -b v4.9.0 --depth 1
cd watchman
./autogen.sh
./configure --enable-lenient --without-python
make
sudo make install

Installation

  • yarn install && yarn setup

Start development version

Start production version

Note: on Windows, add "win-" prefix to the run commands above. For example: npm run win-build. The same applies to other npm run commands below.

Modifying sub-modules and components

After you have changed the files in digitransit-components you have to re-run yarn setup to build those modules and apply the changes.

Analyse webpack bundle

  • run: webpack -p --json > digitransit.json
  • Upload digitransit.json to http://webpack.github.io/analyse/

Or you can also use this:

Using Git Hooks

Husky (npm-package) is used for setting up the git hooks (.git/hooks/) that will allow custom scripts to be run on the repository. Look up 'husky' in package.json to see the details.

Configuration application

Digitransit ui can be configured in multiple ways. You can

  • Change between National and Regional versions using CONFIG parameter
    • Alternatively, use BASE_CONFIG if server is supposed to serve multiple configurations which have same base configuration. It is used server side at start up and request's host specific config based on host or x-forwarded-host header is merged into it before returning config to client.
  • Switch API backend using API_URL parameter
  • Enable Sentry client side error monitoring using SENTRY_* parameters

Note that you can combine multiple configuration parameters.

Changing National/Regional version (optional)

Start national version

  • yarn run build
  • yarn run start

Start HSL version

  • yarn run build
  • CONFIG=hsl yarn run start

Changing urls for OpenTripPlanner, Geocoding, Service alerts and Vehicle positions (optional)

By default digitransit-ui uses services from https://dev-api.digitransit.fi but you can override API server like so:

  • yarn run build
  • API_URL=https://api.digitransit.fi yarn run start

If you want to specify different URL (not just base URL) for individual services, you can define variables OTP_URL, MAP_URL and/or GEOCODING_BASE_URL (URL path before /search or /reverse).

  • yarn run build
  • GEOCODING_BASE_URL=https://api.digitransit.fi/geocoding/v1 OTP_URL=https://api.digitransit.fi/routing/v1/routers/finland/ yarn run start

Using Sentry to track client errors (optional)

Sentry can be configured like so:

Configuring static message URL with env variable

  • STATIC_MESSAGE_URL=https://dev-yleisviesti.digitransit.fi yarn run start