No description or website provided.
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
config
img
info
js
pages
partials
scss
test/e2e
.gitignore
LICENSE.md
README.md
backup.package-lock.json
dev-config.json.template
gulpfile.js
index.html
package.json

README.md

ChronOntology (Frontend)

Prerequisites

The following components need to be installed:

Installation of Dependencies

Install development and production dependencies with the following commands within your ChronOntology frontend directory

npm install

Configuration

cp dev-config.json.template dev-config.json

Running the development server

In order to run the frontend in the development server use the following command:

npm start

ChronOntology frontend will access the production backend and is accessible at localhost:8085/. You can use a different backend instance by setting dataUri and spiUri in dev-config.json (for example to http://localhost:4567 in order to use a local development backend).

Any changes made to HTML, SCSS or JS files should automatically trigger a browser reload.

Running the e2e tests

In order to run the e2e tests use the following command:

npm run e2e

The application has to be already running at localhost:8085/: Either by running npm start in parallel or by deploying and serving a build at that address via your web-server of choice.

Deployment

Build the application by running

npm run build

After building, the ChronOntology frontend lies inside the dist directory.