Oskari Map Application Framework aims to provide a framework and a collection of functionality-enhancing bundles and plugins for rapid development of feature-rich GI web applications.
Documentation available at [http://www.oskari.org].
This repository holds the frontend framework code for Oskari. Developing the frontend framework requires a frontend application. You may clone sample frontend application from [https://github.com/oskariorg/sample-application]. The sample application directory should be located next to the frontend framework directory.
You will also need oskari-server to be running that responds to the XHR requests made by the frontend. You can download a pre-compiled copy of the server from [http://www.oskari.org/download]. You may also build it from source by cloning oskari-server and sample-server-extension.
Oskari frontend applications are built using Webpack.
Make sure you have at least Node 10.x / NPM 5.x.
npm installin the frontend framework repository root.
npm installin the frontend application repository root.
Make sure you have oskari-server running on localhost port 8080 (can be customized on webpack.config.js).
Run in development
Webpack dev server is used to serve the JS bundle and assets when running in local development. XHR calls will be proxied to the Java backend assumed to be running on localhost:8080.
So that the server knows to look for the JS bundle and assets from the right place, we need to have the client version configured in the Oskari-server
To start Webpack dev server run
npm start. The start script in oskari-frontend package.json defaults to the sample application directory but this can be parameterized for custom apps.
When you see "Compiled successfully." in the terminal, you can open the app in the browser at
The dev server has automatic reloading enabled when you save changes to JS code and hot reloading for S/CSS without need for full browser reload.
Build for production
To build minifed JS and assets run:
npm run build.
This will produce optimized files for production under
dist/devapp/servlet/. The build script in oskari-frontend package.json again defaults to the sample application directory. It also defaults to a version named
devapp. Both the app and version number can be parameterized for custom apps.
Note: The version number given for the build command needs to match the client version (
oskari.client.version) in Oskari-server
Special case: If on your production server your application index.jsp location is mapped to something else than the root (eg.
http://yourdomain.com/my-oskari-app/), but the assets are mapped relative to the root (eg.
http://yourdomain.com/Oskari/dist/...), you need to add the build parameter
--env.absolutePublicPath=true like this:
npm run build -- --env.absolutePublicPath=true
Any customized application should use the sample-server-extension template as base for customized server and create an app-specific repository for the frontend.
You can use sample-application template to create your custom frontend application. See further instructions from the sample application repository.
start commands in your application repository root.
Note! All the dependencies (even dev-dependencies like Webpack) are under dependencies for a reason. The reason is that this repository is used as dependency for apps and apps inherit the webpack-dependencies automatically instead of having to install and configure their own versions.
All Oskari-related issues should be reported here: https://github.com/oskariorg/oskari-docs/issues
Please read the contribution guidelines before contributing pull requests to the Oskari project.
This work is dual-licensed under MIT and EUPL v1.1 (any language version applies, English version is included in https://github.com/oskariorg/oskari-docs/blob/master/documents/LICENSE-EUPL.pdf). You can choose between one of them if you use this work.
SPDX-License-Identifier: MIT OR EUPL-1.1
Copyright (c) 2014-present National Land Survey of Finland