Skip to content


Repository files navigation

Sirius Web

Eclipse Sirius Web is a framework to easily create and deploy studios to the web. We keep the principles which made the success of Eclipse Sirius Desktop and make them available on a modern cloud-based stack.

Sirius Web

This repository contains the building blocks from which Sirius Web applications are built. The folder packages contains both the Spring Boot projects from which the corresponding backend is built and the reusable React components used to build the application’s UI. It also contains the Sirius Web sample application.

To test Sirius Web you have two possible options:

  1. If you just want to run an already built version of the example application, follow the Quick Start.

  2. If you want to build the example application yourself, follow the complete build instructions.

Quick Start

If you want a quick overview of how Sirius Web looks and feels like without building the sample application yourself, you will simply need:

  • Java 17

  • Docker, or an existing PostgreSQL 12 (or later) installation with a DB user that has admin rights on the database (those are needed by the application to create its schema on first startup).

Then, download the latest pre-built JAR:

  1. Go to the packages tab of the github project and look for sirius-web-sample-application.

  2. Download the latest jar available

This is a single "fat JAR" named sirius-web-sample-application.jar which contains the complete sample application with all its dependencies.

To actually run the application:

  1. Sirius Web uses PostgreSQL for its database. For development or local testing, the easiest way is to start a PostgreSQL instance using Docker.

    docker run -p 5433:5432 --rm --name sirius-web-postgres \
                                 -e POSTGRES_USER=dbuser \
                                 -e POSTGRES_PASSWORD=dbpwd \
                                 -e POSTGRES_DB=sirius-web-db \
                                 -d postgres:12
    This may take a while the first time you run this as Docker will first pull the PostgreSQL image.

    If you do not have Docker or want to use an existing PostgreSQL installation, adjust the command-line parameters below and make sure the DB user has admin rights on the database; they are needed to automatically create the DB schema.

  2. Start the application:

    java -jar sirius-web-sample-application.jar \
              --spring.datasource.url=jdbc:postgresql://localhost:5433/sirius-web-db \
              --spring.datasource.username=dbuser \
              --spring.datasource.password=dbpwd \
    If you encounter an error similar to org.postgresql.util.PSQLException: FATAL: authentification, check if your 5433 port is already used by another application. If so, change the command lines for docker and the application java launcher with 5434 or any other free port.
  3. Point your browser at http://localhost:8080 and enjoy!

    The initial version of Sirius Web has some known issues with Firefox. It is recommended to use a Chrome-based browser until these are fixed.
Do not forget to stop the PostgreSQL container once you are done: docker kill sirius-web-postgres. Note that this will remove all the data you have created while testing the application.



To build the components in this repository on your own, you will need the following tools installed:

  • Git, and a GitHub account

  • To build the backend components:

  • To build the frontend components:

    • LTS versions of Node and NPM: in particular, Node >= 18.7.0 is required along with npm >= 8.15.0.

    • TurboRepo (npm install -g turbo)

Note that there are issues with NPM under Windows Subsystem for Linux (WSL). If you use WSL and encounter error messages like "Maximum call stack size exceeded" when running NPM, switch to plain Windows where this should work.

For Windows users: Due to the Maximum Path Length Limitation of Windows, you may exceed the limit of 260 characters in your PATH. To remove this limitation, apply the this procedure with this command line in PowerShell (New-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\FileSystem" -Name "LongPathsEnabled" -Value 1 -PropertyType DWORD -Force), then active the longpath option in Git in a command line with administrator rights (git config --system core.longpaths true).

GitHub Access Token

The backend components of this repository depends on sirius-emf-json, which is published as Maven artifacts in GitHub Packages. The frontend components of this repository depends on @ObeoNetwork/react-trello and @ObeoNetwork/gantt-task-react, which are published as Node artifacts in GitHub Packages. To build sirius-web locally, you need a GitHub Access Token so that: * Maven can download the sirius-emf-json and Flow-Designer artifacts. * Node can download the @ObeoNetwork/react-trello and @ObeoNetwork/gantt-task-react artifacts.

  1. Create a personal token with a scope of read:package by following the GitHub documentation if you do not have one already.

    Once generated, a token cannot be displayed anymore, so make sure to copy it in a secure location.
  2. Create or edit $HOME/.m2/settings.xml to tell Maven to use this token when accessing the Sirius EMF JSON repository:

    <?xml version="1.0" encoding="UTF-8"?>
    <settings xmlns=""

    Be sure to replace $GITHUB_USERNAME with your GitHub user id, and $GITHUB_ACCESS_TOKEN with the value of your access token.

    The id used in your settings.xml must be github-sirius-emfjson and github-flow to match what is used in the POMs.
  3. Create or edit $HOME/.npmrc to tell Node to use this token when accessing the Github Node artifacts repository:


    Be sure to replace $GITHUB_ACCESS_TOKEN with the value of your access token.

Build the frontend & backend components and Sirius Web

  1. Clone this repository

  2. Build the frontend packages:

    npm ci
    npx turbo run build
    In order to run tests, use npx turbo run coverage

    To build the package @eclipse-sirius/sirius-components-diagrams the mkdir command is required.

    For Windows users, according to the npm documentation the default value for script-shell configuration on Windows is cmd.exe which does not support the mkdir command. We recommend to use git bash instead of the default command tool.

    Then you can set the script-shell configuration with the following command:

    npm config set script-shell "C:\Program Files\Git\bin\bash.exe"
  3. Install the frontend artifacts as static resource to be served by the backend. From the root directory of the repository:

    mkdir -p packages/sirius-web/backend/sirius-web-frontend/src/main/resources/static
    cp -R packages/sirius-web/frontend/sirius-web/dist/* packages/sirius-web/backend/sirius-web-frontend/src/main/resources/static
  4. Build the backend components.

    mvn clean install -f packages/pom.xml
    If you are behind a proxy, you may get Maven errors about not being available. In this case you need to explicitly disable CheckStyle from the build: mvn clean install -f releng/org.eclipse.sirius.emfjson.releng/pom.xml -P\!checkstyle
    Docker must be installed and running for some of the backend components tests to run. If Docker is not present, you can still build the backend by skipping the tests execution with mvn clean install -f packages/pom.xml -DskipTests.
  5. You can find in the output artifacts in the various target folders of the backend components and the dist folders of the frontend components. You could publish those to your maven or npm repository to consume them in other applications. We are already publishing those components in the NPM and maven repositories of our Github organization.

    Using these instructions, we can find a Spring Boot "fat JAR" in packages/sirius-web/backend/sirius-web-sample-application/target/sirius-web-sample-application-{YEAR.MONTH.COUNT-SNAPSHOT}.jar. Refer to the instructions in the "Quick Start" section above to launch it.


Everything in this repository is Open Source. Except when explicitly mentioned otherwise (e.g. for some resources likes icons which are under Apache-2.0), the license is Eclipse Public License - v 2.0.