Skip to content
master
Switch branches/tags
Code

Latest commit

 

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
 
 
src
 
 
 
 
 
 
 
 
 
 
 
 

687474703a2f2f6936332e74696e797069632e636f6d2f333031336c67342e706e67

linkedpipes-logo

Travis status Codacy Renovate Bot
Guides Frontend Javadoc Apiary

πŸ“ƒ About

LinkedPipes Applications is a visualization web platform that allows the users to explore, visualize and publish LinkedData based visualizer applications. Applications created with these platforms can be easily published and integrated anywhere on the Web!

β€’ General user documentation and platform tutorials are available here
β€’ Developer oriented frontend documentation and React component demos are available here
β€’ Developer oriented backend documentation and architecture overview are available here
β€’ ESWC 2020 Best demo paper LinkedPipes Applications – Automated Discovery of Configurable Linked Data Applications and accompanying poster

πŸš€ Quick start

The faster way to start your own LinkedPipes Applications platform instance is to execute the production docker-compose setup.

Prerequisites

β€’ Docker and Docker-compose

Running within docker-compose

$ curl https://raw.githubusercontent.com/linkedpipes/applications/master/lpa-cli.sh -o lpa-cli.sh && chmod +x lpa-cli.sh && ./lpa-cli.sh --production-no-cloning

Default container ports

Once you have started the instance of the platform in docker-compose, individual components will be accessible on the following ports by default:

You should be able to access:
β€’ Frontend of LPA at localhost:9001
β€’ Backend of LPA at localhost:9005
β€’ Local Discovery at localhost:9000
β€’ Local ETL at localhost:8080
β€’ Local Virtuoso at localhost:8890

🧠 Advanced usage


For more advanced scenarious and executions of development compose configurations it is recommended to clone the whole repository first and refer to documentation of lpa-cli.sh startup commands:

usage: ./lpa-cli.sh [-dc]|[--detailed-command]
-d   | --development                  Start non persistent development setup (assumes repository is already cloned)
-dp  | --development-persistent       Start non persistend development setup (assumes repository is already cloned)
-p   | --production                   Start persistend production setup (assumes repository is already cloned)
-pnc | --production-no-cloning        Start persistend production setup [NO CLONING REQUIRED ;-)]
-cs  | --clean-storage                Remove 'appdata' and 'data' folders with database data and etc
-sc  | --stop-compose                 Setup whatever configuration setup is currently running
-h   | --help                         Print help documentation

πŸ§ͺ Testing

LinkedPipes Applications uses BrowserStack for automated integration testing.

Browserstack-logo-2x